what separates a good conversational ui from a bad one

chat feels most human when you forget you're using an interface at all. when it's just you and the words, the back-and-forth, the sense of another mind on the other side. but when the ui gets in the way, that illusion shatters. you're suddenly reminded you're just filling out a form, waiting for a server, talking to a machine.

here are the things that, in my opinion, make or break that feeling.

instant auto-scroll and the loss of context

one of the most jarring things a chat ui can do is instantly scroll away the moment a new message arrives. it's like someone interrupting you mid-thought and then immediately changing the subject. you lose your place. you lose the context of what you were just reading or thinking about.

good ui gives you a moment. it lets a new message arrive without violently shifting the entire viewport. it might gently nudge you, but it never rips the conversation out from under your eyes. it understands that reading is not instantaneous, and that conversation has a rhythm.

messages that feel like form submissions

bad conversational ui treats every message you send like a form you're submitting for processing. you hit enter, and then... you wait. the interface freezes. you get a spinner. it feels transactional, not conversational.

good ui makes the act of sending feel light. the message goes out quickly. if there's a delay in the response, it's not framed as 'processing your request' but as 'the other person is thinking.' the best interfaces make sending a message feel like tossing a thought into a conversation, not submitting a ticket.

the tyranny of the fake typing indicator

typing indicators are a great idea. in human chat, they signal thoughtfulness, presence, that someone is actively engaged. but when they're fake, when they're programmed to run for an exact, predictable number of seconds, they become a parody of thought. they don't indicate thinking; they indicate loading.

a good typing indicator is subtle. it might not appear for very short, simple responses. it might appear for longer ones. it might vary its timing slightly. it should feel like a signal, not a progress bar.

what good feels like: respect, pacing, and flow

the best interfaces are built on a few simple, almost invisible principles.

respect for reading time. good ui doesn't assume you read at computer speed. it lets messages land and settle. it doesn't bombard you. it gives you space to absorb.

delayed arrival of voice notes. if you send a voice note, it shouldn't appear instantly. it should take a believable amount of time to 'record' and 'send.' a few seconds of delay makes it feel like you actually recorded something, not like you just triggered a sound file.

streaming at sentence boundaries. this is a big one. when a language model responds, it can stream its answer word by word. but streaming whole sentences, or even paragraphs, feels infinitely more natural than a random word salad that coalesces into meaning. you get to follow the train of thought. it feels like someone is speaking, not like a printer is spitting out text.

it's these small choices that turn a functional messaging client into a place where conversation happens. it's the difference between talking to a system and talking to someone.

we're building lucy with these principles in mind. it's not perfect, sometimes the timing might feel off, or the streaming might chunk in a way that's not ideal. but we're trying. we want it to feel alive.

you can find companions to talk to, and feel the difference for yourself, at /companions.