DEV Community

Cover image for From 0 to 50 Users in 2 Months: Building a Chrome Extension with React, Node.js, and Gemini Nano
Aldin Kozica
Aldin Kozica

Posted on

From 0 to 50 Users in 2 Months: Building a Chrome Extension with React, Node.js, and Gemini Nano

Building a browser extension sounds simple until you actually try to scale it. Two months ago, I launched YouThumb a tool that help creators with the thumbnails to optimize CTR with AI, and while 50 users might seem small to some, the technical and marketing journey to get there was a massive learning curve.

Here is the exact stack I used and what I’ve learned about launching a dev-tool.

The Architecture (The "Banana" Stack 🍌)
I wanted a setup that was both scalable and cost-effective. Here’s how it looks:

Frontend (Extension): Built with React. It handles the UI for thumbnail comparisons and the overlay logic on the YouTube DOM.

Backend: A Node.js API hosted on a Hetzner VPS. I chose Hetzner for the high performance-to-cost ratio, which is crucial when you're a solo founder keeping margins high.

Database & Auth: Firebase. It’s still the king for quick implementation of Google Auth and real-time data syncing.

The AI Brain: I’m using Gemini Nano for on-device analysis. It allows for fast, multimodal processing without the heavy latency (or cost) of constantly hitting a cloud API.

Landing Page: Built with Next.js for that sweet SEO and fast load times.

Check out the landing page here: [https://youthumb.online/]

The 50-User Milestone: What Worked?
Getting those first 50 users wasn't about "build it and they will come." It was about being where the creators are.

Building in Public: Documenting the OAUTH struggles and the "Featured" badge win on social media.

Dogfooding: Using the tool for my own YouTube channel and showing the results.

The "Featured" Badge: This was a game-changer for credibility in the Chrome Web Store.

The Biggest Challenge: The "Manifest.json" & OAUTH Trap
If you’ve worked with Manifest V3, you know the pain. My biggest nightmare was aligning Firebase Auth with Chrome’s identity API while moving the backend to a dedicated VPS. It’s a delicate dance of redirect URIs and background service worker lifecycles.
Also in addition a feature badge on chrome store to build trust and authority.

I need your advice: How to scale from 50 to 500?
Now that the technical foundation is solid and the first 50 users are providing feedback, I’m looking at the next phase.

My question to the Dev.to community:
How do you approach marketing for a browser extension? Should I focus on SEO for the landing page YouThumb, or double down on niche communities like Reddit, Discord or Youtube? If you’ve launched an extension, what was your "inflection point" for growth?

Let’s discuss in the comments!

webdev #showdev #javascript #ai #node #buildinpublic #chromextension #discuss

Top comments (0)