Earlier quoted context omitted.
I suspect there are many, many things for which chat is a great interface. And by positioning ChatGPT as the distributor for all these things, they get to be the new Google. But you're also right that many domains for which a purpose-built interface is the right approach, and if the domain is valuable enough, it'll have someone coming after it to build that.
I have yet to see a chat agent deployed that is more popular than tailored browsing methods. The most charitable way to explain this is that the tailored browsing methods already in place are the results of years of careful design and battle testing and that the chat agent is providing most of the value that a tailored browsing method would but without any of the investment required to bring a traditional UX to fruit…
At least in my domains, the "battle-tested" UX is a direct replication of underlying data structures and database tables.
What chat gives you access to is a non-structured input that a clever coder can then sufficiently structure to create a vector database query.
Natural language turns out to be far more flexible and nuanced interface than walls of checkboxes.