Skip to content
AppDues
Log in
Contact salesSign up

RocketSim's Indie Growth: Time Saved, Roadmap Votes, and the Full-Time Trap

RocketSim began as a personal utility for the Xcode simulator and grew into a paid product approaching $100K in annual recurring revenue, with no traditional ad spend or influencer campaigns. In a Launched podcast conversation with Charlie Chapman, developer Antoine van der Lee walks through the decisions behind that growth: how he frames the product's value, how a public roadmap shaped what he built next, and why leaving his day job initially made him less productive rather than more.

Selling time, not features

Developer tools often struggle to explain what they actually sell. Is it a nicer interface? A different workflow? Antoine's answer is narrower: RocketSim reduces the time a developer spends on simulator-related work and returns that time to feature development.

That framing matters because it changes what the buyer compares. A feature list asks a developer to adopt a new habit. A time calculation asks a manager to multiply a small daily saving across a team and a year. The second comparison is easier to defend in a budget conversation.

A practical checklist for applying this to your own tool:

  • Name the specific task your product shortens, not the category it belongs to.
  • Estimate the saving per person per day, then show it across a team and a year.
  • Tie the recovered time to work the buyer already wants done, such as shipping features.
  • Avoid claiming a saving you cannot trace to a concrete step in the workflow.

The underlying idea is that time is the constraint most teams cannot expand, so a product that gives time back has a clear reason to be paid for.

Letting users choose the next feature

Rather than picking the next feature from personal preference or a new API, Antoine kept a public roadmap and let users vote. The top-voted request was a network monitor.

When it shipped, the reported effect was measurable: active trials moved from about 40 per day to about 120 per day. That figure is the guest's own account of what happened after the release; treat it as a reported result rather than an independently audited metric.

The mechanism is worth separating from the number. A voted roadmap does three things at once:

  • It tells you which missing capability is blocking the most people.
  • It gives people who left for a specific gap a reason to return.
  • It turns a release announcement into a direct answer to a request users already made.

A simple decision rule: if a feature request keeps appearing across support threads, reviews, and churn reasons, it is a candidate for the roadmap. If it only appears in your own wish list, it is a candidate for later.

The feature that took two years

One RocketSim capability sat as an open GitHub issue for two years: slowing the simulator's network without slowing the rest of the Mac. Existing answers covered general network throttling, but not a simulator-only version.

Antoine did not force a workaround. He kept the issue open, talked to other developers at conferences, and waited for the platform APIs that would make a clean solution possible. When it finally worked, the payoff came from persistence as much as technical skill.

The transferable lesson is about sequencing, not stubbornness. Some problems are blocked by missing platform support, and the right move is to keep the requirement documented and revisit it when the underlying tools change. Others are blocked only by effort, and those should be solved now. Distinguishing the two prevents both premature hacks and abandoned ideas.

Why more hours did not mean more output

The common picture of going full-time indie is five uninterrupted days a week for the app. Antoine made the leap after matching his salary and building RocketSim to nearly $100K in recurring revenue, and found the opposite of the expected boost.

Without the scarcity of nights-and-weekends work, the habits that had made him effective slipped. Prioritization and planning dropped away, and days started without a decided focus. The constraint that had forced ruthless choices was gone, and output did not rise to fill the space.

A checklist for keeping the side-project discipline after going full-time:

  • Keep a written priority list even when the calendar looks open.
  • Block time for the single most important task before checking messages or requests.
  • Preserve a hard boundary on scope per week, as the side-project schedule once did.
  • Review at the end of each week whether the hours produced shipped work or only activity.

The point is not that full-time indie work is a mistake. It is that the structure has to be rebuilt deliberately once external time pressure disappears.

Using this page

The page includes share buttons for X and LinkedIn, a copy-link control, a table-of-contents selector that jumps between the sections above, and a newsletter signup form that asks for a business email address. The guest links point to Antoine van der Lee's X profile, the RocketSim site, and the SwiftLee blog.

Frequently asked questions

What is RocketSim?

RocketSim is a developer tool that extends the Xcode simulator. It was created by Antoine van der Lee, who also writes the SwiftLee iOS development blog.

Did the network monitor feature really triple daily trials?

The guest reported that active trials went from roughly 40 per day to roughly 120 per day after the network monitor shipped. That is his account of the result, not an independently verified measurement, so use it as a directional example rather than a benchmark.

Why did one feature stay open for two years?

The goal was to slow the simulator's network without affecting the rest of the Mac. General throttling answers existed, but a simulator-only solution depended on platform APIs that were not yet available. Antoine kept the issue documented and revisited it when the tooling caught up.

What changes when an indie developer goes full-time?

The external time pressure that forced prioritization disappears. In Antoine's case, planning and prioritization lapsed and daily output did not increase. The practical response is to rebuild explicit priorities and weekly scope limits rather than assuming an open calendar produces more shipped work.