> If you can narrow the problem down, then you could design a much better interface for it than a text box and free form text (unless that's the better solution).

Yes, I agree, in that the chatbot we built probably would have worked just as well with a traditional UI, and would have been done a lot faster. But it would have been a lot less sexy (actually important for the bottom line!) and there are future directions that could take advantage of the conversational interface that’s potentially better than a traditional UI.

On the down side, good chatbots are really frikkin difficult to write. These things (LLMs) are not reliable at scale. The basic functionality came together in weeks. Getting it to behave consistently and obey guardrails took months, and even then we had to accept a low level of failed conversations.

> But it would have been a lot less sexy (actually important for the bottom line!

That’s what the author have been saying. They do for nice demos which sell the illusion of having Jarvis in text format, but the usefulness is not really proven. And that may be important business wise. But as far as end users is concerned, there’s not a lot of productivity boost.