Most AI chatbots are designed incorrectly.
They’re just websites shoved into a chat window.
Remember the early “mobile web”?
Brands didn’t design for mobile — they just crammed the desktop site into a tiny screen.
Pinch. Zoom. Mis-click. Pain.
It took the iPhone era (and mobile-native patterns) for the internet to finally look like it belonged on a phone.
I think we’re repeating the same mistake with AI chatbots.
Right now, the default instinct is:
stuff the website inside the chat window.
So you get things like:
– comparison tables in a tiny chat panel
– checkboxes and mini-UI clones of the PDP/PLP
– “website features”… but worse, because chat isn’t built for that
My take: chat is a new form factor, and it needs native patterns.
At Alhena, we’re opinionated about this:
✅ The chatbot should complement the page
❌ not duplicate it
❌ and never conflict with it
If the page already shows specs, don’t repeat specs in chat.
Use chat for what the page can’t do well: clarification, guidance, tradeoffs, confidence, “what should I pick and why?”
Curious how other builders are thinking about this: