Skip to content
AppDues
Log in
Contact salesSign up

Sebastian Röhl on HabitKit: quitting, pivoting, and going full-time indie

Sebastian Röhl left a corporate programming role in 2021 to test whether he could build a mobile app business. His first app, Liftbear, stalled. His second, HabitKit, eventually grew enough for him to become a full-time indie developer. The contrast between the two launches is the useful part: one showed weak demand despite sustained effort, while the other produced early attention, then search-driven growth.

Leaving the corporate world

In 2021, Röhl was a full-time corporate programmer who wanted more creative control over his work. He liked conceiving a product, deciding how to solve a problem, building it himself, and seeing the result used in the real world. He had some savings for living costs, so he resigned and allowed himself 12 months to create a mobile app business.

A fixed runway matters because it turns a vague ambition into a test with a deadline. It also creates a decision point: if the business has not produced enough evidence by the end of the period, returning to employment is a planned fallback rather than a failure to commit.

If at first you don't succeed

Liftbear was Röhl's first release. It averaged roughly 10 downloads a week and earned $100 over six months. He kept working on it for several months, adding features, improving the app store listing, and promoting it on Instagram. Those efforts did not change the underlying demand.

The distinction is between execution problems and demand problems. Features, listing changes, and promotion can help an app that people already want. When downloads remain low after those levers have been tried, the more likely explanation is weak product-market fit. Röhl concluded after six months that he needed to change direction if he wanted to continue with an app business.

Early success signals

Röhl gave himself two months to build and launch HabitKit. Sharing screenshots while building in public produced an early signal: the first image of the main screen received 800 likes on Twitter. That response suggested stronger interest than Liftbear had generated.

HabitKit then made $1.5k in its first month, more than Liftbear had made in six months. The amount alone did not settle the question, because Röhl was approaching the end of his 12-month runway. He returned to his former job and continued developing HabitKit as a side project.

Useful early signals to compare include:

  • Attention before launch, such as saves, shares, or likes on build-in-public posts
  • Downloads and revenue in the first month, measured against the previous app
  • Whether interest persists after the initial announcement
  • Whether growth comes from a repeatable channel rather than a one-off spike

Becoming a full-time indie developer

In June 2023, about two months after Röhl returned to work, HabitKit began ranking in the top five search results for a major keyword. Downloads and revenue rose sharply. By September, the app was earning thousands of dollars a month, and Röhl again considered leaving his job. He took a couple of months to decide, partly because he valued his employer and colleagues, but concluded that the numbers left him little choice.

By the end of 2023, HabitKit had reached 120k downloads and $51k in revenue. From January to May 2024, it brought in $110k. His next steps were to add features, strengthen app store optimisation, and build community through social media and email marketing.

A practical quit-or-stay checklist drawn from this sequence:

  • Is there a repeatable source of demand, such as search ranking, rather than only launch attention?
  • Has revenue remained strong for several months?
  • Can the app continue growing while you are employed?
  • Have you considered the effect on your employer and team?
  • Is there a clear plan for features, discoverability, and community after you leave?

The takeaway: launch quickly, read the signal, pivot sooner

The central lesson is to test demand quickly and be willing to pivot. A poor launch does not always mean the idea needs more polish; it may mean there is not enough product-market fit to support a subscription business. Learning that early lets a developer move to a more promising concept instead of spending many more months on an app with little traction.

Röhl's path was not a single leap from employment to independence. He used savings and a deadline, tested one app, recognised weak demand, built a second app in two months, returned to work when the runway ended, and left again only after search-driven growth had continued for months. That staged approach reduced the risk of quitting while still allowing him to act when the evidence changed.

Frequently asked questions

When did Sebastian Röhl decide to quit his corporate job?

He had savings for living expenses and set a 12-month window to build a mobile app business. When that window neared its end, he returned to his previous job and continued HabitKit as a side project, then left again after sustained growth made full-time work viable.

How did Liftbear and HabitKit compare?

Liftbear averaged about 10 weekly downloads and made $100 in six months despite new features, listing optimisation and Instagram marketing. HabitKit, by contrast, drew strong early attention, made $1.5k in its first month, and later grew through search visibility.

What does a lacklustre launch signal?

A weak launch can indicate insufficient product-market fit for a subscription business. Launching quickly, watching early demand, and pivoting sooner can save months spent improving an app that users are not adopting.