Comment by rco8786
12 hours ago
I think there's a lot of potential in AI as a UX in that way particularly for complex apps. You give the AI context about all the possible options/configurations that your app supports and then let it provide a natural language interface to it. But the result is still deterministic configuration and code, rather than allowing the AI to be "agentic" (I think there's some possibility here also but the trust barrier is SO high)
The gmail filters example is a great. The existing filter UX is very clunky and finnicky. So much so that it likely turns off a great % of users from even trying to create filters, much less manage a huge corpus of them like some of us do.
But "Hey gmail, anytime an email address comes from @xyz.com domain archive it immediately" or "Hey gmail, categorize all my incoming email into one of these 3 categories: [X, Y, Z]" makes it approachable for anyone who can use a computer.
> You give the AI context about all the possible options/configurations that your app supports and then let it provide a natural language interface to it.
If it's "AI" I want more than that, as i said.
I want it to read the email and correctly categorize it. Not just look for the From: header.
My second example was "Hey gmail, categorize all my incoming email into one of these 3 categories: [X, Y, Z]"
Missed it, but I think you're thinking of something easy like separate credit card bills by bank and all into their own parent folder.
I've had multiple times email exchanges discussing status and needs of multiple projects in the same email. Tiny organization, everyone does everything.
Headers are useless. Keywords are also probably useless by themselves, I've even been involved in simultaneous projects involving linux builds for the same SoC but on different boards.
I want an "AI" that i can use to distinguish stuff like that.