¥50K/Month After 5 Years: An Indie App's Tactics That Worked — and the Ones That Didn't

The Numbers First

Item	Figure
Monthly revenue	¥50K
Since first app release	5 years
Since monetization began	~2 years
Interim milestone	¥10K/month
Revenue model	Three pillars: ads + subscriptions + one-time purchases

The developer, who goes by Dokozono, deliberately keeps the app’s name, genre, and download count private while disclosing revenue figures and the outcomes of each tactic. His consistent claim: “There are no super techniques. Persistence is everything.”

What Worked

Placing the payment prompt right after use. He added paths to the payment page immediately after the main feature is used and at first launch. It is the textbook conversion design — pitch at the moment the user feels the value — executed faithfully in a small app.

Collecting requests via an official LINE account and shipping them as features. A standing contact channel continuously gathered user feedback. This “always-open support desk,” rare in indie development, appears to have paid off in reviews and retention.

Joining the Apple Small Business Program. Under the program, developers with annual sales of $1 million or less see Apple’s commission drop from 30% to 15%. Just applying multiplies take-home revenue by roughly 1.2x — the first move any indie developer in early monetization should make.

What Didn’t Work (This Is the Valuable Part)

Defaulting the purchase screen to the annual plan → no effect. The reason is clear: this app sits in a low-frequency genre where “a few uses a month is a lot.” The appeal of an annual plan only works for high-frequency apps. A real-world case showing that standard growth-hacking plays whiff when they don’t fit the app’s usage context.

A/B testing → no significant differences. In his words, “at this scale it’s hard to get a meaningful difference.” With the user base behind ¥50K a month, statistically meaningful experiments are all but impossible to run. Improvements to a small app have to run on user feedback and qualitative judgment, not data.

What to Take From This

“Five years to ¥50K a month” is the median pace of indie development. Behind the dazzling success stories, most indie projects move at this speed. What matters is his explanation of why he kept going for 5 years: “revenue arriving and user reviews were the motivation.” How quickly you earn your first yen and your first kind review is the lifeline of persistence.

Three revenue pillars are a rational survival strategy for small apps. Combining ads (a thin layer from all users), subscriptions (a thick layer from heavy users), and one-time purchases (catching subscription-averse users) lets each model cover the others’ weaknesses. The fewer users you have, the more it matters to hold multiple routes to monetizing a single user.

A record of tactics that failed carries more information value than a success story. Annual-plan defaults and A/B tests are staple recommendations in growth articles. The report that both are ineffective under the conditions of “low-frequency app x small scale” directly saves time for developers in the same situation. Read alongside the education app that grew to ¥4.61M a year, it becomes clear that indie projects that take off are decided less by tactical skill than by choosing a high-frequency usage domain.

Conditions for Reproducing It — and the Limits

Easy to reproduce: the Small Business Program, the post-use payment prompt, and the contact channel are three moves any app can apply starting today
Limits: with the app’s genre and download count undisclosed, we cannot verify what kind of market produced this pace. ¥50K a month is not a life-changing amount; whether you treat it as a goal or a waypoint changes the strategy