In July 2026 I started building GrowX, a Chrome extension that helps creators and founders grow a relevant audience on X (formerly Twitter). I'm a full-time student, so every decision had to fit around classes and exams. Four months later the extension is live on the Chrome Web Store, and I've learned more about product building, browser engineering and distribution than any course has taught me. Here are the lessons I'd share with any student thinking about shipping a side project.
1. Start from a workflow you already do by hand
GrowX didn't start as an idea. It started as a chore. I was trying to grow my own X account, and the only thing that reliably worked was finding people who had recently followed creators in my niche, checking whether they were active and real, and engaging with them. It worked, but it took an hour a day.
When a manual process works but costs too much time, that's a strong signal for a product. You already know the steps, you know what "good" looks like, and you are your own first user. Every feature in GrowX maps to a step I used to do myself: source targeting, filtering by activity and profile quality, and tracking who followed back.
2. Make the core logic explainable
The heart of GrowX is a follow-back score from 1 to 99. I could have tried to build something clever and opaque. Instead I built a weighted score from a handful of signals anyone can understand: follow ratio, recent activity, whether an account has a real photo and bio, and how similar it is to accounts that followed you back before.
Explainable logic paid off in three ways. Users trust a number they can reason about. Bugs are easy to find, because when a score looks wrong you can see which signal caused it. And I could ship it in days instead of weeks. For an early product, "simple and transparent" beats "smart and mysterious".
3. Local-first is a feature, not just a cost saving
As a student I couldn't afford servers, so GrowX stores everything in the browser's own storage. There's no account to create and no backend holding anyone's X data. Follower snapshots, scores and settings never leave the user's machine, and backup is a JSON file they control.
What started as a budget constraint turned into one of the things users mention most. People are tired of handing their social accounts to third-party dashboards. Keeping data local made the product easier to trust and easier to explain.
4. Learn your platform's constraints early
Chrome's Manifest V3 replaced always-on background pages with service workers that the browser can suspend at any moment. My first scheduler kept losing its place. The fix was to treat every step as resumable: wake up with chrome.alarms, read state from storage, do one small unit of work, save state, and go back to sleep.
The broader lesson is that every platform has rules that shape your architecture, whether that's a browser, an app store or a social network's own policies. Reading them on day one saves a rewrite on day thirty. It's also why GrowX defaults to slow, human-paced activity with daily caps, active hours and an emergency stop: X's rules apply to every user, and the product should respect them by design.
5. Measure what actually drives results
I added analytics to GrowX mostly for myself, and it changed how I grew my own account. When I tracked which source accounts brought real follow-backs, I found that two out of ten were responsible for most of my growth. I had been spreading effort evenly across all of them.
The same applies to building a product. I now track which launch channels send visitors to growxapp.org, and the answer is rarely the one I expected.
6. Distribution is half the work
I underestimated this badly. Building the extension took weeks; getting anyone to see it is an ongoing job. Over the past few weeks I've listed GrowX on startup directories, written technical articles about how the follow-back score and unfollower tracker work, and shared it in communities that welcome makers.
What I've learned: be honest that it's your own project, give people something useful even if they never install it, and don't expect any single launch to change everything. Search visibility compounds slowly.
7. Protect your time
Exams don't move for product launches. I keep a short daily list (one piece of content, a few listings, one useful post) and automate what I can. Shipping small and steady has worked far better for me than weekend sprints followed by weeks of silence.
What GrowX does today
GrowX is free on the Chrome Web Store. It includes source-based audience targeting with filters, the 1-99 follow-back score, an unfollower tracker, a post scheduler with active hours, growth analytics, and an on-device writing helper. Premium options come with a 30-day free trial.
Website: growxapp.org
Chrome Web Store: GrowX on the Chrome Web Store
If you're a student building something on the side, I'd love to hear what you're working on and what's been hardest for you. And if you try GrowX, honest feedback is the most useful thing you can give me.
Top comments (0)