Congrats on the launch!
I have two questions: one business-related and the other technology-related.
1. Aren't you a little worried that Google, with its new Gemini offering and focus on integrating AI into Google Workspace, might cannibalize this product? Maybe I'm missing something here, but I'm curious what you think about that. Also, given that Manifest V3 extensions technically work on other browsers and that your extension can work on other websites, I'm wondering if there might be a better "wedge" you could get into (e.g. Proton Mail on Firefox, etc).
2. Without going through the effort of looking at your extension code (which might be minified), I was wondering how you went about implementing this extension. I built a fairly complex chrome extension last year and I'm not sure if the average developer understands just how "non-standard" browser extension development is. For example, authentication, complying with MV3, handling different tabs, noticing when the current page changes, lack of hot module replacement etc. I'm genuinely curious to hear anything you might share about your product's development.
Cheers!
Hi Josh, thank you for your feedback :)
1. You’re totally right to flag the potential overlap with Google’s Gemini and its integration into Workspace — it’s something we’ve thought a lot about. Google is definitely making strong moves here, but we see our opportunity not in replacing Gemini, but in building an AI layer that works across tools and ecosystems, not just within Google’s walled garden.
While Gemini is powerful inside Workspace, we think many users — especially knowledge workers and power users — don’t live exclusively inside Google’s tools. They might draft in Google Docs, communicate in Proton Mail, manage tasks in Notion, and read articles in Firefox. That fragmented workflow is exactly where our extension shines: by giving them a consistent, context-aware AI assistant wherever they are, not just inside Google’s UI.
You also make a good point about extension portability. We’re definitely exploring alternative “wedges” and distribution channels — like targeting users who prefer privacy-first tools (e.g. Proton Mail, Firefox), or platforms where the incumbents have less AI integration.
So in short: yes, we’re aware of the risk — but we believe there’s still a meaningful opportunity in offering a more flexible, cross-platform assistant that complements rather than competes directly with the big players’ native solutions.
2. For auth, we're using Clerk (which is a bit less well supported in extensions than we'd like, but works well enough), and the Chrome 'Identity' API to allow you to OAuth with Gmail.
Complying with MV3 isn't too hard to achieve, and the Chrome store has a fairly robust review process. They have a 'slow queue' for reviewing apps that request higher permissions (like ours has to) which means shipping hotfixes isn't really possible! It's usually a 48 hr loop to get new code deployed.
Re. hot module replacement we're using https://wxt.dev/ which is built on top of Vite and has been really good. Seamless dev experience with all the affordances you expect in modern web dev tooling. Would definitely recommend.
Cheers