built the whole thing with no frontend and it turned out the frontend was the part i was hiding behind

shipped dexi, an assistant that lives in imessage. no app, no dashboard, no settings screen. the entire "frontend" is text messages

the reason i'm posting it here: building with no ui exposed how much of my usual process was decoration. normally when something feels off you adjust spacing, add a loading state, write helper text, put in a toggle. all of that is real work that also functions as a place to hide a weak core. strip the interface and there's nowhere to put the polish. the thing either understood the sentence or it didn't

concretely what changed in how i build. i stopped shipping features and started shipping sentences, because every capability has to be expressible as something a person would actually type without being taught. if a feature needs explaining, it doesn't exist. that killed about a third of my roadmap and the product got better

second thing: no ui means no place for settings, so every configuration decision has to become a default that's right for most people, or be inferred. that's harder and it's also the correct pressure, i'd been using settings as a way to avoid making decisions

honest downsides so this isn't a victory lap: no visual output at all, nothing that needs a table or a chart works, and discoverability is genuinely bad because there's no menu to browse. users don't know what it can do and i can't show them without being annoying

if you're building conversational stuff, my one takeaway is that the constraint is worth trying even temporarily. delete the ui for a week and see which features survive being un-illustratable