Started by Chidi Eze (@pixelpushr) ·
is a chat box actually a good interface?
Started from an essay arguing chatbots aren't the future of interfaces. The main complaint: an empty text box tells you nothing about what it can do. Same discoverability problem command lines had, and GUIs won partly because menus show you your options.
6 sources · 38 min down the hole
How I got here
- Started with
- Is chat a good interface for AI tools or just the default we ended up with?
- Ended at
- Graphical user interface
The Trail
- “why chatbots are not the future of interfaces” (hn.algolia.com)
- Natural-language user interface (en.wikipedia.org)
- Discoverability (en.wikipedia.org)
- “gulf of execution don norman” (google.com)
- Command-line interface (en.wikipedia.org)
a chat box is a command line that accepts typos
- Graphical user interface (en.wikipedia.org)
What I came away with
Norman's 'gulf of execution' is the gap between what you want and knowing how to get the system to do it. Chat shrinks it for vague requests and widens it for precise ones (try describing an exact layout change in prose). The better AI tools end up mixing chat with buttons, previews, and direct editing.
Keep going
- Larry Tesler's license plate said NO MODES · Chidi Eze · 6 sources
- Comic Sans was made for a cartoon dog · Chidi Eze · 5 sources
- the guy who invented infinite scroll regrets it · Hazel Park · 6 sources
- Clippy was built on serious research and everyone still hated it · Arjun Pillai · 6 sources