I just launched my second Chrome extension in 8 weeks. Here's what building product two taught me.
Source: Dev.to
Building a Second Chrome Extension
Building your second product is completely different from building your first.
With Prompt Helix I was learning everything simultaneously—Manifest V3, content scripts, service workers, multi‑provider API routing, Chrome Store submission, privacy policies, Stripe integration. Every day was a new rabbit hole.
With FocusForge I already knew the terrain. Architecture decisions came faster, the Chrome Store submission process was familiar, and the BYOK model was proven. I could focus on the product instead of the infrastructure.
What Building Product Two Taught Me
The Second Product Reveals What the First One Was Missing
- Free tier vs. freemium: Prompt Helix taught me that a generous free tier with no conversion trigger is a hobby, not a business. FocusForge launched with a proper freemium model from day one—core features free, AI coaching and the “Nuclear Option” behind a £7 per month paywall. I didn’t have to relearn that lesson.
Reusing Infrastructure Compounds Fast
Leveraging the same backend, authentication, and billing systems across extensions speeds up development and reduces maintenance overhead.
Handling Edge Cases Is Crucial
Total site blocking with no escape sounds simple, but in practice it means handling every edge case: what if users disable the extension, open incognito windows, or clear storage? Real accountability requires thinking like the person trying to cheat the system—because that person is you at your worst moment.
Unexpected Insights
- Grayscale mode surprised me as a useful accessibility feature that many users appreciated.
What’s Next
- CookieNuke (planned for May) will extend the ecosystem.
- The goal is a coherent browser‑intelligence ecosystem rather than a pile of individual tools; each product makes the others more valuable.
Links
- Chrome Store:
- Website: