Live data from Hacker News

Show HN: I made an email app inspired by Arc browser

demo.define.app

1–10 of 54 posts

Show HN: I made an email app inspired by Arc browser

#1
Email is one of those tools we check daily but its underlying experience didn’t evolve much. I use Gmail, as probably most of you reading this.

The Arc browser brought joy and taste to browsing the web. Cursor created a new UX with agents ready to work for you in a handy right panel.

I use these three tools every day. Since Arc was acquired by Atlassian, I’ve been wondering: what if I built a new interface that applied Arc’s UX to email rather than browser tabs, while making AI agents easily available to help manage emails, events, and files?

I built a frontend PoC to showcase the idea.

Try it: https://demo.define.app

I’m not sure about it though... Is it worth continuing to explore this idea?

Show HN: I made an email app inspired by Arc browser
demo.define.app

Re: Show HN: I made an email app inspired by Arc browser

#5
Well done!

I do hope AI will really allow folks to build products with better UX. The problem traditionally is that the UX gets "stuck" - gmail, google maps, they cannot really change because of user's expectations and the big orgs that run them as products. And building new things from scratch was fairly expensive. But now with AI (and modern UI tooling) the equation is at least partially changing.

Re: Show HN: I made an email app inspired by Arc browser

#10
> [email's] underlying experience didn’t evolve much

In stories of architecture, this is the beaten path that becomes the walkway.

> Is it worth continuing to explore this idea?

It has to be worth it to you.

If you open-source it, you get to articulate what's important and shift from doing to leading. That's a forcing function to state values that inspire people.

For me, UI is a frustrating 1:N problem, where 1 designer(s) make trade-off's for many users. You're bound to get some early accolades, but expanding surface area scales mainly to frustrating everyone in some manner.

I'd like a UI that settles per user or use-case: automatically pruning things I don't use and hoisting things I do, often adapting use-case driven patterns. (The eclipse IDE UI had workspaces suited to different activities, and Mylyn task-based UI which hide or highlighted resources in the workspace for a given task; and that task context could be shared, e.g., attached to a bug, so anyone working on the bug would see (only) the relevant files or methods.)

The key question is what's different now with AI. Email or DB forms are presenting data in ways you can arbitrarily explore.

But when co-working with others or AI, it's more about watching messages and command streams between users, agents, etc, with varying levels of detail. AI is more about queueing up and automating interactions with a given intent. So in this case I'd e.g., enforce a GTD workflow by making queues for simple or hard, with contingencies on approvals or work, spawning actions that reply, and some ways to correlate related streams. To scale you need completion functions, archives, task debt tracking, etc. so you're always starting with a clean slate but someone can always pick up where you left off.

The thing about email is that it has mostly outlived a bazillion contenders, because the data conventions are dead simple and it has relevance built in, where each message (should) start with next steps and provide necessary context (intent and context: sound familiar?). And they're queued in your inbox, giving you instant organization (urgent X important). Combine it with markdown...

Post reply on HN