Function calls are the unsung hero of LLM UI manipulations. While OpenAI has made great strides leveraging function calls to manipulate the UI in their demos, the rest of industry is yet to take its first meaningful steps. But what do those steps look like?
Most chatbots stick to one modality—either text or voice. But as someone who uses subtitles for everything, I wonder why voice bots don’t also include text for accessibility. Is it a limitation in the voice tech stack? Does text clutter the UI? To find out, I decided to build my own streaming-first chatbot interface with both text and voice.
The other day on Discord, I was trying to convince someone that they should not build a chatbot. Crazy, right? But here’s the thing: Chatbots are an interface, just like buttons and tabs, and just like other interfaces, there are times when they do more harm than good. Just imagine if your phone’s settings app was a chatbot, and you had to type in a message or a talk to it just to enable or disable airplane mode?