What I learned building a Chrome extension for X growth as a student founder

In July 2026, a student founder began developing GrowX, a Chrome extension designed to help creators and founders expand their presence on X (formerly Twitter). As a full-time student, every decision had to be balanced with classes and exams. After four months of development, the extension was launched on the Chrome Web Store, providing the founder with valuable lessons about product building, browser engineering, and distribution. Here are the key takeaways shared by the student:

1. Begin with a task you already perform manually: GrowX originated from the founder's need to grow their own X account, which required manually finding and engaging with recently-followed accounts from their niche. The manual process, although time-consuming (about an hour a day), proved that the product would work. Every feature in GrowX corresponds to a step in the founder's previous manual efforts.

2. Make the core logic understandable: The heart of GrowX is a follow-back score ranging from 1 to 99. Instead of building an complex, opaque score, the founder opted for a weighted score based on easily understandable signals such as follow ratio, recent activity, real profile photos and bios, and similarity to accounts that followed back before. This approach fostered trust, made it easier to identify bugs, and allowed for quick deployment.

3. Local-first is a feature: Given limited resources as a student, GrowX stores all data locally in the browser's storage. There's no account creation or backend storing users' X data. Snapshotting follower lists, scores, and settings within the user's machine, along with a JSON backup file that the user controls, turned a budget constraint into a trust and explainability asset.

4. Understand your platform's constraints: Chrome's Manifest V3 replaced always-on background pages with service workers that can be suspended at any moment. The student's initial scheduling approach led to losing track of progress. The solution was to create resumable tasks: wake up, read state from storage, execute small units of work, save state, and go back to sleep. This teaches the importance of understanding platform rules early in the development process.

5. Measure what drives results: Initially, the founder added analytics mostly for personal insights. However, the data revealed that only two out of ten source accounts were responsible for most of the growth. This same principle applies to building a product; tracking which launch channels bring visitors to a specific site can provide valuable insights.

6. Distribution takes time and effort: Building the extension was time-consuming, but attracting users is an ongoing task. The founder listed GrowX on various startup directories, wrote articles about its features, and shared it in relevant maker communities. Growth is slow and steady, requiring consistent distribution efforts and realistic expectations about the impact of any single launch.

7. Prioritize your time: With classes and exams, protecting your time becomes crucial. The founder follows a daily routine, focusing on creating one piece of content, submitting listings, and sharing useful posts. Automation has helped streamline tasks, allowing for consistent progress without overwhelming the schedule.