HabitKit's Slow-Burn Growth: What Sebastian Röhl's Path Teaches Indie Developers
HabitKit's rise looks sudden only in retrospect. Before it, Sebastian Röhl shipped a workout tracker that plateaued, returned to employment, and kept building. This guide walks through the decisions that mattered and turns them into a checklist you can apply to your own app.
From a stable job to a self-imposed deadline
Röhl studied computer science and software engineering in Germany, then spent three years in enterprise software working with C#, .NET, and Angular. The job gave him solid engineering habits and exposure to experienced colleagues, but it wasn't the work he wanted long-term. He left without a defined product idea and set one constraint: twelve months to make something work. Mobile apps were the medium he chose, not a specific niche.
The first app: stalled, not failed
LiftBear was a workout tracker built for personal use. Röhl shipped it fast, skipped beta testing, and promoted it by posting progress on Twitter. It found a small audience and settled around $150 in monthly recurring revenue. Six months of updates produced no meaningful movement. That is the key distinction: the app wasn't dead, but it also wasn't sending a signal that more effort would change the trajectory. Röhl describes the period as demotivating for exactly that reason.
HabitKit: one visual, immediate resonance
HabitKit began with a narrow idea — a habit tracker that showed consistency through a GitHub-style contribution grid. When Röhl shared an early screenshot, engagement jumped and new followers arrived. That pre-launch interest was the first clear signal he had. He committed fully and shipped the first version after roughly two months. Day-one revenue was about $150 — modest by startup standards, but proof that people grasped the product on sight.
Building in public helped early, then handed off to organic discovery
Public progress posts gave HabitKit its first users, early ratings, and momentum, and kept Röhl accountable during quiet months. But the largest growth event came from elsewhere. Months after launch — by which point Röhl had returned to a four-day-a-week job — HabitKit started ranking for "habit tracker" in several App Store regions, including Germany and the UK, with Google Play following shortly after. There was no viral post and no metadata change he could point to. Röhl still doesn't know the trigger. What he observed is that once the app crossed a threshold, downloads and revenue accelerated, and earlier work on quality, reviews, and consistency finally converted into distribution.
The return to employment, and the second exit
When the twelve-month deadline ran out, HabitKit couldn't yet support Röhl full time. He went back to his previous company four days a week and kept Fridays for his apps. That fallback bought stability and time. Six to seven months later, organic discovery was compounding and revenue was climbing steadily enough that he felt confident leaving again — this time on traction rather than hope.
FocusKit: novelty as maintenance, not diversification
After years of near-exclusive focus on HabitKit, Röhl noticed his own motivation stalling. Updates had become incremental and public writing felt repetitive. FocusKit, a minimalist Pomodoro timer built natively in SwiftUI, was his way to learn new technology, lean into native iOS design, and recover creative momentum. It was not meant to replace HabitKit or match its revenue. The launch was deliberately low-pressure, early revenue has been modest, and the project's real function is keeping him engaged and shipping.
A decision checklist for a stalled app
Use this to separate the two situations Röhl encountered — a plateau with no signal, and a plateau that precedes compounding.
- Is there any pre-launch or early signal of instant comprehension? HabitKit's screenshot response was the clearest indicator Röhl had. LiftBear had nothing comparable.
- Has effort produced movement in the last six months? LiftBear's updates did not shift revenue. If repeated iteration leaves the number flat, more iteration is unlikely to be the answer.
- Is the product's value legible in one image or sentence? HabitKit's grid communicated consistency without explanation.
- Are the fundamentals — quality, reviews, consistency — in place before you expect distribution? Röhl's ranking shift arrived after those had accumulated, not before.
- Can you afford a fallback that preserves building time? A reduced-schedule job gave Röhl both stability and Fridays.
- Is a side project serving motivation or diversification? FocusKit was explicitly the former, and judging it by HabitKit's revenue would misread its purpose.
Worked example: reading the LiftBear-to-HabitKit pivot
LiftBear reached roughly $150 in monthly recurring revenue and stayed there through six months of updates. HabitKit reached roughly $150 on day one. The figures are similar; the signals are not. LiftBear's number was a ceiling reached after sustained effort. HabitKit's number was a floor established before any ranking shift, and it was accompanied by visible pre-launch interest. The lesson isn't that $150 means something specific — it's that the direction and context around a number matter more than the number itself. When a metric is flat despite effort and the product isn't instantly legible, starting over can be the higher-value move. When a metric is small but the product resonates and fundamentals are accumulating, patience is more likely to pay.
What to watch when ranking shifts without a launch event
Röhl could not identify a trigger for HabitKit's App Store ranking change. That makes the event hard to replicate deliberately, but not impossible to monitor. Track these fields so a shift is visible when it happens:
- Keyword position by store and region (HabitKit appeared in multiple regions, including Germany and the UK).
- Store surface: App Store first, Google Play following.
- Download and revenue trend before and after the shift.
- Review volume and rating trajectory, which reflect accumulated quality.
- Any metadata or marketing change in the preceding weeks, so you can rule causes in or out.
If a shift occurs with no corresponding action on your side, treat it as a distribution signal to reinforce rather than a mystery to solve.
Frequently asked questions
Did LiftBear fail?
Not in the sense of shutting down. It attracted a small user base and settled around $150 in monthly recurring revenue. The problem was the absence of growth: six months of updates didn't change the trajectory, which left no signal that further investment would pay off.
What made HabitKit's early screenshot resonate?
The concept was a habit tracker that visualized consistency as a GitHub-style contribution grid. That single visual communicated the product's value immediately, and the public response — engagement and new followers — gave Röhl clear pre-launch interest.
Was building in public the main growth driver for HabitKit?
It was critical early on, supplying first users, initial ratings, accountability, and motivation. The largest growth moment, however, came later and organically: HabitKit began ranking for "habit tracker" in multiple App Store regions, with Google Play following, and Röhl could not identify a specific trigger.
Why did Sebastian Röhl go back to a job after the twelve-month deadline?
HabitKit could not yet support him full time when the deadline expired. He returned to his previous company four days a week and reserved Fridays for his apps. Six to seven months later, with organic discovery compounding and revenue climbing, he left again — this time on evidence rather than hope.
Was FocusKit meant to diversify revenue?
No. FocusKit, a minimalist Pomodoro timer built natively in SwiftUI, was a way to learn new technology, lean into native iOS design, and restore creative momentum after years of near-exclusive focus on HabitKit. Early revenue has been modest and the launch was intentionally low-pressure.