How Rootd reached 2M downloads without funding, employees, or coding
Ania Wysocka built Rootd, a panic attack and anxiety relief app, to more than two million downloads without outside capital, without hiring an employee, and without learning to code. The useful lesson is not simply to spend less: it is to match each growth attempt to relevance, timing, and a story other people can repeat.
Start with piecemeal help instead of waiting for a big budget
A $40,000 development bid was initially offered, but Ania judged it insufficient for the full build. Instead of waiting for a larger budget, she worked with a student developer early on and later brought in help in small, separate contracts only when a specific task required it. That pattern kept fixed costs low while still allowing progress.
Use this as a decision rule: separate the product you must ship from the help you can buy in pieces. If a single quote bundles everything, ask which parts are essential now, which can wait, and which can be handled through a narrow contract. The point is to avoid letting an all-or-nothing budget decide whether the app exists at all.
Relevance beats keyword volume in ASO
Paying a contractor for ASO strategy produced the opposite of the intended result. The problem was not experimentation itself; it was chasing higher-traffic keywords that were less relevant to Rootd. Those terms could attract people who were unlikely to want or keep the app, and downloads fell.
The better trade-off was narrower: choose keywords closely tied to panic attacks and anxiety relief, even when search volume was lower. Early users who found the app through relevant terms helped fuel rapid growth because they matched the product's purpose. Before changing keywords, check relevance first, then volume, then watch downloads after the change rather than assuming bigger traffic is better.
Build organic discovery through press, timing, and persistence
With no advertising budget, Ania looked for earned attention. Local journalists who covered small-business success offered a natural fit, and important dates and national events gave announcements a reason to be timely. She planned a year of monthly press releases and product-feature announcements across a season, turning launches into a steady calendar instead of occasional posts.
For Editor's Choice, persistence mattered. After 15 submissions, she was told to prepare artwork because a feature might be imminent. When featured, Rootd saw a direct, correlatable rise in browse installs. Treat repeated, well-prepared submissions as part of the work: keep assets ready, keep submitting, and measure browse installs around any feature.
Tell a story people can repeat, then repeat what works
A clear story makes sharing easier. New features gave Ania something concrete to announce, and even difficult press placement did not end the effort. Her advice, in paraphrase, is to repeat what produces a bump until that bump becomes normal: do the effective thing well, do it often, and keep going.
A practical checklist follows from that approach: name the user problem in one sentence, tie each feature to that problem, connect announcements to a date or event when possible, prepare store artwork before you need it, and track whether each attempt produces installs or repeatable attention. The episode also covers what best signals retention, but the supplied text does not specify that signal, so it is not guessed here.
| Approach | What happened | Decision rule |
|---|---|---|
| High-traffic, less relevant ASO keywords | Downloads fell in the reported case | Check relevance before volume |
| Highly relevant, lower-volume keywords | Early matched users contributed to rapid growth | Prefer smaller, well-matched demand |
| Local press plus timely events | Provided organic promotion without ad spend | Plan announcements around dates and features |
| Repeated Editor's Choice submissions | Feature was followed by more browse installs | Keep artwork ready and keep submitting |
Reported outcomes from the episode account; not independently verified current figures.
Frequently asked questions
Did Rootd grow without funding or employees?
No. The account describes reaching more than two million downloads without outside capital or hiring an employee, using piecemeal contracting when needed.
Which ASO keywords worked better for Rootd?
Highly relevant keywords with lower search volume. Higher-traffic but less relevant keywords were linked to weaker results and, in the reported case, a fall in downloads.
What organic channels drove discovery?
Local journalists interested in small-business stories, timely dates and national events, feature announcements, and repeated submissions for an Apple Editor's Choice feature.
What was the small change that increased revenue fivefold?
The episode summary reports a fivefold revenue increase from one small change, but does not identify the change in the supplied text, so it should not be guessed.