Solo app developer growth: email list, support, and review lessons
Joe Allen built Teleprompter Pro without a computer science degree, a marketing budget, or a formal plan. The app still became his full-time business. This guide pulls out the repeatable parts of that story: a simple utility born from a real video-production problem, an email list that gave him a direct line to users, personal support that doubled as product research, and a subscription transition that did not depend on App Store release notes. It also covers the less comfortable side: in the podcast episode, Allen describes an App Store Review fight for his new app that took two weeks to resolve.
From a freelance workaround to a 15-year business
The durable lesson from Teleprompter Pro is not that a clever idea wins. It is that a narrow, unglamorous tool can compound for years if it keeps solving the same job. Allen's starting point was a low-budget pilot shoot in 2010 where he needed scrolling text and found his improvised setup on a first-generation iPad awkward, down to the missing black background. He had recently downloaded Xcode, so he wrote a minimal scrolling-text app himself.
The first version only moved text upward. On the App Store alongside other random projects, it was the one that gained traction because it solved a real problem for people doing video production. For the next seven years it produced steady organic revenue while Allen worked full-time in web and graphic design. In 2018, the app's revenue let him quit that job and go full-time indie.
Read that timeline as a patience test rather than a launch story. The product did not need a large launch. It needed a genuine job to do and enough time for organic demand to accumulate.
The App Store is a river, not a scoreboard you control
It is tempting to credit every download spike to the feature you just shipped. Allen takes a humbler view. Developers often assume everything happening to them is something they caused, he notes, when the App Store is really a massive river. Sometimes an app is simply sitting in the current, lifted by a small algorithmic tweak or a new search trend.
He accepted that early. Even during years when he barely updated the app, he says there was never a day of zero revenue. That does not mean the algorithm is fair or predictable. It means the practical response is to build a reliable product and let organic momentum do more of the work, rather than chasing every algorithm change.
A useful distinction for any solo developer:
- Developer-caused movement: a feature, price change, or email campaign you can trace to a decision.
- Platform-caused movement: a search trend, ranking tweak, or seasonal shift you did not control.
- Baseline demand: the steady revenue a utility earns because it keeps solving the same problem.
Separating these three keeps you from over-learning from a spike or panicking over a dip.
Personal support is product research with a goodwill bonus
After going full-time, Allen spent a large share of his working days answering support email. Many messages were simple, such as explaining that a user's orientation lock was on. He still felt responsible for giving every user a helpful answer.
That direct line became his most valuable research channel. He worried that unanswered simple questions would turn into one-star reviews or abandoned subscriptions. Instead, the conversations surfaced real product needs, including a video recording option and better onboarding.
The second effect was harder to measure but just as important: users who started out frustrated often became loyal advocates because a real reply came from the app's creator rather than an automated corporate response.
A practical support checklist:
- Answer the simple questions anyway; they are often the ones that become public complaints.
- Tag recurring questions by theme so patterns become visible.
- Turn repeated confusion into onboarding changes, not just replies.
- Keep the reply personal when the team is small enough to allow it.
Why an email list is the safety net
If Allen insists on one piece of advice, it is owning your audience. From the early days he asked users for an email address, not because he had a grand marketing plan, but because he liked being able to announce things to people. He calls that decision the single most important thing he did for his career.
The list mattered most at transition points. In 2020, when Teleprompter Pro moved from a paid upfront model to a subscription model, he did not have to rely on App Store release notes. According to the episode, he could email users directly, explain that existing customers were grandfathered in, and offer a discount to people on the fence. Those 2020 grandfathering and discount terms are historical source-reported facts; any current offer terms require owner confirmation.
More recently, when he launched the new app Captions (Recap), the episode reports that he emailed a segmented list of users who actively record video and offered the Pro upgrade free to those who pre-ordered. That pre-order promotion is a historical source-reported event, not a live offer; any current promotion requires owner confirmation.
The App Store algorithm can change overnight. An email list means you never have to start from zero.
A worked example of the 2020 transition shows what each message had to do:
- Explain the change: paid-upfront users needed to know what happened to their purchase.
- Protect trust: grandfathering existing customers removed the fear of being punished for buying early.
- Convert the undecided: a discount gave fence-sitters a reason to move.
- Keep the channel warm: the same list was reused years later for a new app launch.
None of that required a large marketing budget. It required collecting addresses early and treating the list as a relationship rather than a broadcast pipe.
The App Store Review fight behind a new launch
The full episode also covers the stress of an unexpected spam rejection from App Store Review for Allen's new app, the value of attending industry events, and why slow, steady growth is often the healthiest path for indie developers. In the episode, Allen describes the rejection taking two weeks to resolve, including a phone call that finally cracked it.
That is a reminder that launch plans can collide with review outcomes outside your control. A useful preparation step is to keep a direct support or review contact path and to separate the product work from the review fight so a delay does not stall everything else.
Frequently asked questions
When should a solo developer start an email list?
As early as users are willing to share an address. In this case the list was built long before it was needed for a pricing change, which is what made it useful when the subscription transition arrived.
Is personal customer support worth the time for a small app?
It can serve two purposes at once. It reduces the risk that simple confusion turns into bad reviews, and it reveals recurring product gaps such as missing recording options or weak onboarding.
How did the email list help with the move to subscriptions?
According to the episode, it let the developer explain the 2020 change directly, confirm that existing customers were grandfathered in, and offer a discount to undecided users without depending on App Store release notes. Those terms are historical source-reported facts; current terms require owner confirmation.
What happened with the App Store Review rejection?
The new app received an unexpected spam rejection. In the podcast episode, Allen describes it taking two weeks to resolve, including a phone call that finally cracked it.