define

After long months of work, we are ecstatic to share our vision for the future of email and work communication. Try here: demo.define.app I’d genuinely love to hear what you think, especially if you use email for work! Note: this is a frontend demo with mock data. PS - Reposting this because the previous video included sensitive mock data.

@mrterrycarson Thank you Terry! We haven’t launch yet, we do have a demo to showcase our idea and learn from folks as early as possible 🙌

@define_app Congrats on the launch! Tabs and smart folders sound super useful. Can’t wait to try it and see how the AI handles my inbox chaos.

We are building a new email app. ▫️Tabs keep priorities separated and focused ▫️Smart folders organize work automatically ▫️AI agents take action for you A new email app is coming! Try it here: define.app

@ducatapp Thank you 🙌

@define_app The tabbed layout looks quite nice, tbh.

@istupidpreneur Gotcha! What would be ideal for you?

@define_app the whole thing feel like a chore now. it's suddenly now a project management tool.

@istupidpreneur Interesting! What part feels complicated? Genuinely asking because we’re trying to simplify things 😅

@define_app am the only one who think this is complicated?

@wonotna @NotionMail @NotionHQ Thank you so much! 😎

@define_app This is what @NotionMail @NotionHQ should build… @define_app great job! App looks amazing 🤩 can’t wait to try it 😗

@maksrybicki Hopefully this Summer 🤞

@define_app Do you have any ETA on when you plan to launch the beta tests for users?

@saurav__codes @whereistejas Wow, you already have a solid setup. Define basically abstracts that flow so teams don’t have to manage SES/Lambda/S3/DNS plumbing themselves.

@define_app @whereistejas not sure if i understood it correct, but i have amazon ses inbound dns record configured to rec email & using aws lambda to save them in s3. for sending email, i have configured mx records on my domain provider. so is there is any blog available for how you catch inbound emails?

We’ve been bootstrapping for 9 months. Why is it taking us so long to launch? In one word: Craft. We're building: - a web app - an iOS app - a macOS app And also: - The best multimodal search in the industry - Agent infrastructure for on-demand assistance Be the first to try it: define.app

@shutupraster @gettravelapp Of course 🥰

@define_app can we try it at @gettravelapp

@KostjaPalovic @saurav__codes That’s exactly how we think and the main reason why we’re building define. Thank you so much for sharing!

@saurav__codes @define_app although, bootstrapping is tough, so good luck of course with this product. email is hard. making it nice to use is hard. and we haven't seen fresh email products in a while. Sparrow is something that i miss from 10-15 years ago.

@saurav__codes Oh yea, we’ll support SMTP x.com/define_app/sta…

@define_app how is it different from superhuman, spark and other email app providers?

@ParssaKyanzadeh Omg! DM’d you. Thanks for sharing.

@define_app pls fix

@nedymax Yes, we’re starting with business email first. Are you more interested in checking it for personal email?

@define_app And it requires a business domain to get early access? So, is that only for businesses?

@nedymax Yep, pretty much. I’m super stoked you find it simple, half the problem is solved 🙌 Tabs and folders are just the start.

@define_app So, is this just a mail app but with tabs and “smart” folders?

@nicu_tsx @ZaynHao Oh, what a nightmare. There’s definitely a lot of internal coordination needed. I hear you!

I guess all this animosity towards non-web apps is due to my personal experience in adding some new login modal at my previous job. 1. modal in landing page (react) 2. similar modal inside the web game (but preact) 3. same modal inside the ios app (swift) 4. same modal inside the android app (react native) 5. the existing modal in the web game that runs inside the ios app in a webview (so preact with swift bindings) 6. I think the webview integration with android was a bit simpler so just due to the fact that the team/organization existed in this way, a "simple" implementation was spent on just making the same thing work correctly in multiple different flows

@nicu_tsx @ZaynHao Not at all. I was genuinely interested in your take. And I understand your point. Software is becoming a commodity, so experience matters more than ever. To me, that means taking the time to craft the best possible version for each platform.

@define_app @ZaynHao maybe this is a take that's too spicy, I'm sorry for that

@nicu_tsx @ZaynHao Yes, they won’t be pixel perfect and we are ok with it. Can you elaborate on what’s not “crafty”?

@define_app @ZaynHao that means you're implementing the same thing twice, doesn't sound very crafty. Also the mental model from react and swift is very different meaning you'll definitely introduce slight differences or need to have expensive testing suites

@ZaynHao Good question. I think it depends on your users. For the people I’ve talked to, macOS was usually preferred. They want something faster, more native feeling, and easier to keep in their daily workflow.

Thanks for your reply. My question is: is a macOS app important enough for your users? Maybe a web app is totally enough to use. I'm curious about the decision. Because I'm facing a similar dilemma. I developed a card note-taking app. It has a web version now, but I'm torn on whether to provide a macOS client version.

@saurav__codes Have you played with it? demo.define.app Would love your thoughts on why/how it's different.

@simplydt Let's hope you are right 🙏

@define_app craft wins, juggling web, iOS, macOS inevitably extends runway