The most common question I get from people building their first app with Rork is: "How should I monetize this?" I've been shipping iPhone and Android apps independently since 2014. There were stretches where I crossed ¥1.5M/month on AdMob, and stretches where I switched to subscriptions for steadier income. What I've learned is simple but hard to internalize: which monetization channel works isn't about which one is "best" — it's about what genre and user base your app actually has.
This guide compares five monetization channels for the kind of apps Rork is well-suited for — wallpaper apps, calming apps, life-loggers, mini-utilities. The implementation deep-dive and the eight specific steps I took to reach ¥1.5M/month on AdMob live in the companion article. This article is purely about choosing the right channel.
The Five Realistic Channels for Indie Mobile
In day-to-day indie work, your real options are:
- Ad revenue (AdMob, Unity Ads, AppLovin, etc.)
- In-app purchases (one-time unlocks, coin economies)
- Subscriptions (monthly / yearly)
- Paid downloads (price the app itself in the store)
- Sponsorship and brand tie-ins (native, contracted directly)
Affiliates and merch sales exist in theory but rarely move the needle for the kinds of apps Rork excels at building, so I'm setting them aside.
1. Ads (AdMob Is Still the Default)
In 15+ years of running indie apps, ads have been the easiest channel to ship and the one with the highest upside ceiling.
This channel suits apps with these traits:
- High MAU — ad revenue scales with impressions, so light, frequently used apps win
- Genres where users expect free — calculators, weather, wallpapers, daily reminders
- Short, frequent sessions — three to ten minutes per session pairs cleanly with ad formats
It does not suit deep games, social apps, or chat apps, where ad interruption tanks retention and ARPU.
In 2026, the ad-format priority I'd recommend is:
- Rewarded video — by far the highest eCPM, lowest UX harm
- Interstitials — full-screen, between-screen ads. Easy to overdo
- Banners — alone they barely move revenue, but cheap to add
- Native ads — woven into list views; more implementation effort, better feel
When my wallpaper app was hitting ¥1.5M/month, the mix was roughly 70% rewarded, 20% interstitial, 10% banner. Whether you can build rewarded video into your core flow more or less determines your ad ceiling.
2. In-App Purchases (IAP)
Three core patterns: remove ads, unlock features, buy coins. For Rork-style utility apps, the "remove ads" IAP is the most common starting point.
In Japan specifically, the sweet spot for the "remove ads" IAP is ¥300–¥500. Once you cross ¥1,000, conversion drops sharply. This isn't a global truth — Western users will pay more — but the principle of finding your local price ceiling holds everywhere.
IAP suits apps with:
- Necessary but visible ads — if your app has no ads, no one wants to pay to remove them
- Long-lived usage patterns — single-session apps don't generate enough buying intent
- Engaged core users — IAP often functions partly as "fan support"
In my own wallpaper app, the ¥350 "remove ads" IAP was a steady several-tens-of-thousands of yen per month, sitting alongside the main ad revenue. I think of IAP as a complement to ads, not a replacement.
3. Subscriptions
Both stores have pushed hard toward subscription models in recent years. The genres that subscribe well in the Rork-built world are:
- Content-additive apps — wallpaper packs, daily reminders, meditation tracks, anything where new content arrives weekly
- Cloud-sync apps — notes, expense trackers, life loggers benefit from cross-device sync as a paid feature
- AI-powered apps — monthly token allowances make a natural subscription tier
The Japanese market price band is roughly ¥480–¥980 monthly, ¥3,800–¥8,800 annually. Past ¥1,500/month, only clearly business-critical apps survive.
The biggest subscription trap is first-month churn. Japanese users have unusually high resistance to subscriptions, and 20–40% first-month cancellation is normal. A 3- or 7-day free trial isn't optional — and the in-trial onboarding flow is what actually decides whether they convert.
I tried a "premium themes ¥480/month" subscription on one of my wallpaper apps and it failed because the trial-period experience wasn't compelling enough. My current view is that subscriptions are 90% onboarding scenario design, 10% engineering.
4. Paid Downloads
Charging for the app itself in the store. In 2026 it's genuinely hard to make this work as a sole monetization model. The dominant pattern is "free, with ads or IAP," and users default to that — paying upfront has become a niche behavior.
It still works in three pockets:
- Business utilities — invoicing apps for solopreneurs, measurement tools for tradespeople
- Education apps — instrument tutors, language drills, flashcards — categories with surviving paid culture
- Premium games — polished puzzle or adventure titles
Japanese sweet spot: ¥120–¥600. Past ¥1,200 the curve falls off a cliff.
For Rork-style casual apps, my honest take is that paid downloads are usually the wrong choice. A free-with-ads-and-IAP combo will outperform on long-run revenue almost every time.
5. Sponsorship and Brand Tie-ins
This one is under-discussed in indie circles but works in specific genres. I know a fortune-telling app developer who runs a "monthly contract with a named astrologer brand, content embedded in-app" deal worth around ¥200,000/month. Several meditation app developers run similar tie-ins with audio brands.
The conditions for sponsorship to work:
- Tightly-scoped genre — your audience matches a specific brand's audience
- Content-additive structure — you can swap monthly content blocks
- MAU above ~10,000 — enough scale that a brand sees the placement as worth paying for
Implementation is trivial: reserve a content slot, swap the sponsor's content monthly. The hard part is sales — you negotiate directly with the brand, not through an ad network like AdMob.
How to Choose — A Decision Order
Stepping back, here's the order I think through when advising other indie developers:
- Will MAU plausibly exceed 10,000? → If yes, ship AdMob first
- Can you add weekly content? → If yes, run a subscription alongside ads
- Are users asking to remove ads? → If yes, ship a remove-ads IAP
- Is it a business or education app? → If yes, paid download is on the table
- Does the genre match a brand's target? → If yes, look for sponsorship
Combining channels is the default strategy, not a sign of indecision. Even my ¥1.5M/month AdMob app ran IAP simultaneously. Choosing only one channel is simpler but always worse for total revenue.
Failure Patterns I Keep Seeing
A few recurring mistakes from talking to other indie developers:
Going subscription-first with no audience. Pre-MAU-1,000, locking the app behind a subscription throws away the ad revenue you could be earning at zero marginal cost.
Ad density too high. Chasing eCPM by raising frequency tanks store ratings, which suppresses store discovery, which reduces installs. Long-run negative.
Pricing too high. ¥1,500 IAPs and ¥1,500/month subscriptions are above the Japanese conversion ceiling. A/B test multiple price points in soft launch before committing.
Stacking too many ad SDKs. Bundling AdMob + Unity + AppLovin balloons your binary size and slows cold start. I generally just use AdMob for everything.
What to Do Next
If a channel is now standing out as the right fit for your app, the next step isn't writing more code. It's writing three numbers on paper: target MAU, target ARPU, target monthly revenue.
MAU × ARPU = monthly revenue. If you can't fill that equation in for your app, you're not yet ready to seriously monetize. If you can fill it in and the numbers feel reachable, you have a real plan.
For the implementation specifics — and the eight concrete steps I took to grow one app from zero to ¥1.5M/month on AdMob — see the companion article. It's the realistic version, with the failures included.