You have a working chat interface in an afternoon. Turning it into a product users pay for takes months. The gap isn't the model: it's conversation history, citations, cost guards, and the boring auth and billing layer nobody talks about.
What a Real Chatbot Product Has to Handle
Streaming Chat UI
Token-by-token rendering is the baseline. You need SSE or fetch streaming, Markdown rendering mid-stream with code blocks and syntax highlighting, a stop button, regenerate, edit-and-resend, and scroll-to-bottom that respects where the user scrolled. The Vercel AI SDK handles all of this. Don't roll streaming yourself.
Conversation History
Not a single chat: a list of chats with a sidebar, new-chat button, rename and delete, folders or categories, search across conversations, pinning, and optional public sharing.…