Comment by nottorp

10 hours ago

Heh, I would love to just be able to define email filters like that.

Don't need the "AI" to generate zaccharine filled corporatese emails. Just sort my stuff the way I tell it in natural language.

And if it's really "AI", it should be able to handle a filter like this:

if email is from $name_of_one_of_my_contracting_partners check what projects (maybe manually list names of projects) it's referring to and add multiple labels, one for each project

4 comments

nottorp

Reply
rco8786  9 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.

  • nottorp  9 hours ago

    > 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.