iOS is not where the money is. Not for everyone. Not anymore.
That's a hard thing to say out loud in 2026, when every developer on X is vibe-coding iPhone apps and the iOS bootcamp industry is booming. But Steve — the founder of Journalable, an AI calorie counter — built his app to $100,000 a month in revenue and 80% of it came from Android. Not 51%. Not 60%. Eighty percent.
He didn't stumble into this. He made a calculated decision, followed the data, and built a system. This article breaks down exactly what he did — and what it means for anyone building a consumer app in 2026.
1. What Is Journalable — and Why Should You Care?
Journalable is an AI-powered calorie counter. You type in what you ate. You take a photo of your meal. The app identifies ingredients, estimates portions, and gives you the full calorie and macro breakdown. You can also log exercise. That's it. No complex database search. No manual entry of every ingredient. Just: input food, get numbers.
Simple? Yes. Boring? Apparently not. The app now has close to one million downloads on Android alone, over 30,000 active subscribers, and generates approximately $125,000 in revenue within a single 28-day period — giving it an MRR of around $80,000 and an ARR approaching $1 million.
Steve, the co-founder, didn't come from a tech background. He came from lived experience. He once weighed 125 kilograms. He lost 45 of them — roughly 100 pounds — by tracking calories religiously. During that process, he used nearly every major calorie tracking app available and found all of them unnecessarily complex. Journalable was built to solve the exact problem he had personally faced: a best-in-class nutrition tool with zero unnecessary friction.
The personal pain-point origin story is common in startup circles. What's less common is the discipline to keep the product genuinely simple even after revenue starts flowing. Steve kept it that way. The Health & Fitness category on the Google Play Store is littered with bloated calorie apps. Journalable's competitive edge isn't AI — it's restraint.
2. Why Android? The Data Steve Actually Looked At
Here is the conventional wisdom: iOS users have more money, spend more on apps, and are worth targeting first. That's not wrong as a general statement. But it's incomplete — and for a bootstrapped founder, it can be financially fatal.
Steve and his co-founder looked at a specific data point from the RevenueCat State of Subscription Apps 2025 report: iOS users cost roughly four times more to advertise to than Android users. Yet their subscription conversion rate is only about 20% better. The math here is not subtle. You are paying 4x for a 1.2x advantage. If you are running on your own money, that is a bad trade.
Steve also discovered something specific to his business: running Android ads on Google's network generated spillover installs on iOS. Some users who saw the Journalable ad in Google's ecosystem happened to be iOS users and still downloaded the app. That meant his iOS revenue wasn't costing him iOS ad spend — it was a free byproduct of his Android campaigns.
The result today: 80% of Journalable's users and 80% of its revenue come from Android. The 20% iOS share is essentially organic. For anyone still defaulting to iOS-first without running the numbers, Steve's story is a data-backed counterargument.
3. The 6-Step Google Ads Playbook
Steve spent just under $500,000 on Google Ads over Journalable's lifetime. The revenue directly attributed to those ads is nearly identical — making the campaigns essentially break-even on acquisition while organic growth and subscriber renewals generate the actual profit. Here is the exact playbook he described, step by step.
Step 1 — Set Up Attribution and Measurement First
Before spending a single dollar on ads, connect your app's event tracking to Google Ads. This means telling Google's system when a user installs the app, reaches the paywall, starts a free trial, and completes a purchase — including the transaction value. Without this data layer, Google's algorithm is running blind. With it, the algorithm can optimize delivery toward users who actually pay, not just users who download and delete. This step is not optional. It is the foundation everything else is built on.
Step 2 — Launch Install Campaigns to Feed the Algorithm
Google Ads App Campaigns need volume to learn. Start with install campaigns — their sole job is to generate downloads and give the algorithm a baseline understanding of your market: what an install costs, what the CPM looks like in your target country, who is clicking. You need to supply the campaign with assets: five headlines, five descriptions, up to 20 images, and up to 20 videos. If you don't have custom creative yet, stock images and stock video work fine at this stage. The goal is to start the machine, not win a design award.
Step 3 — The Asset Optimization Phase
Start with a small daily budget — $10 to $15 — and let the campaign run while you build better creative assets in parallel. The critical instruction here: take big swings. Do not A/B test minor details like font size or button color. Test radically different visuals, different value propositions, different emotional angles. The algorithm will surface what resonates. When patterns emerge from the data — one image significantly outperforming others, one headline generating more trial starts — that is your signal on what messaging actually converts your specific audience.
Simultaneously, update your Play Store assets. Your app title, subtitle, screenshots, and description directly feed Google App Campaigns. A mediocre Play Store listing undermines even the best ad creative.
Step 4 — Launch a Target CPA Campaign
Once your assets are performing consistently, shift to a Target CPA (Cost Per Acquisition) campaign. This tells Google: "Acquire users who complete this specific action — a trial start or a purchase — and optimize toward that cost target." To run this campaign effectively, your daily budget must be at least 10 times your target CPA. If a free trial costs you $15 to acquire, you need $150 per day minimum. This isn't a guideline — it's a hard technical requirement for Google's algorithm to receive the 10 daily conversion events it needs to optimize properly. Running a tCPA campaign on an insufficient budget produces garbage results.
Step 5 — Scale Budgets Gradually
After one to two months of consistent campaign performance, you will have real CAC data. That is when you start scaling. Increase budgets in line with Google's best practices — typically no more than 20% increases at a time — to avoid destabilizing the algorithm's learning phase. If you have access to external funding, this is where it accelerates things. If you are bootstrapped like Steve, growth is slower but the unit economics are cleaner because every dollar spent has to return a dollar.
Step 6 — Optimize the Product Conversion Rate Continuously
The flywheel only keeps spinning if your subscription conversion rate keeps climbing. Test your paywall design. Test your pricing. Test your trial duration. As your conversion rate improves, the same ad spend generates more paying subscribers — which means you can afford to raise budgets and acquire even more users. The system feeds itself. This is not a "set it and forget it" operation. It requires constant iteration on the product side in parallel with the ads side.
![[recommended size: 1000×560px] 📸 IMAGE PROMPT: Overhead flat-lay diagram of a minimalist Google Ads funnel — 6 sequential rectangular cards labelled Step 1 through Step 6, connected by thin orange arrows, printed on off-white matte paper. Cards show icons: a tracking pixel, a Play Store icon, a bar chart, a target crosshair, a dollar sign, a circular arrow. Cold neutral lighting, clean editorial layout. Mood: systematic, analytical. Style: Bloomberg Businessweek infographic, flat illustration. No faces, no screenshots, no text in the image, no stock feel.](https://blogger.googleusercontent.com/img/a/AVvXsEjpf6XurIjSdwfXxYor1ZeBWUdA87TwN8qUOLEbFkyx8Eu1WaWIp7KGBR6HgLrr5WEM9E04FE16lf1CQKzE1ayUBh4EAdDu76El3T-h8lKFYQw7BbpuqqHMsCgGhR4Hydh4Ru7k7vRnW-E9TYbEYzFipoAdvJhaRhK-lwn8hLUMDcNIMg1ZWrCTn6wCux5d=w640-h358-rw "[recommended size: 1000×560px] 📸 IMAGE PROMPT: Overhead flat-lay diagram of a minimalist Google Ads funnel — 6 sequential rectangular cards labelled Step 1 through Step 6, connected by thin orange arrows, printed on off-white matte paper. Cards show icons: a tracking pixel, a Play Store icon, a bar chart, a target crosshair, a dollar sign, a circular arrow. Cold neutral lighting, clean editorial layout. Mood: systematic, analytical. Style: Bloomberg Businessweek infographic, flat illustration. No faces, no screenshots, no text in the image, no stock feel.")
4. The Android Opportunity in 2026 — Bigger Than You Think
Steve made an observation that gets lost in the noise: the explosion in vibe-coded, AI-assisted apps is almost entirely an iOS story. According to the RevenueCat State of Subscription Apps 2026 report — which analyzed over 115,000 apps and $16 billion in revenue — iOS now accounts for approximately 77% of all new subscription app launches, up from 67% in 2023. Monthly new subscription app launches have grown roughly seven times since January 2022, but Android's share of that growth is shrinking. AI coding tools appear to default to App Store-first, which is flooding iOS with new competition every week.
The practical implication: for most categories, if a successful iOS app exists, there is probably no equally polished Android equivalent. That gap is Steve's core thesis for where the opportunity lies. Build the Android version of something that already works on iOS. You already have proof of demand. You already know the monetization model. You just have to build it for a platform where the competition is less crowded and the advertising costs are a fraction of iOS.
There is a second opportunity beyond that. The lowering cost of software development means niche problems that were previously too small to justify building an app for are now economically viable. A hyper-specific problem shared by a small but definable group of users — if no one has solved it cleanly on Android — is a legitimate business. You do not need a million downloads. You need the right ten thousand.
Steve also mentioned localization as an underexplored growth lever. Expanding to France, South America, Southeast Asia — these are growing markets where top English-language apps have not yet built proper local experiences. Android users in these regions are substantial in number. Their LTV is lower than North American users on average, but their acquisition cost is dramatically lower too. The RevenueCat 2025 data shows that revenue per install in India and Southeast Asia is about $0.11 at Day 60 versus $0.55 in North America — but the cost-per-install differential in these markets can offset that gap for the right apps.
5. The Tech Stack Behind a $1M/Year App
One of the more useful parts of Steve's conversation was the complete breakdown of his monthly tool spend. For a business doing close to $1 million ARR, the operational cost structure is remarkably lean.
| Tool | Purpose | Monthly Cost |
|---|---|---|
| Firebase + GA4 | Backend + Analytics | Variable (GCP) |
| RevenueCat | Subscription management | Variable |
| OpenAI | Backend AI (calorie analysis) | Variable + $20/mo |
| Claude Code + Cowork | AI-assisted development | $100/mo |
| GitHub Copilot | Code completion | $39/mo |
| CodeRabbit | AI code review | $30/mo |
| Fixer | AI email support | $30/mo |
| n8n | Operations automation | $24/mo |
| AppFollow | App Store Optimization | $180/mo |
| Webflow | Landing page / website | $18/mo |
The total fixed tool spend is under $450 per month, excluding variable API and cloud costs. For a subscription app generating $80,000 MRR, that is a negligible operational overhead. The biggest recurring expense by far is Google Ads — which Steve frames not as a cost, but as a near-break-even customer acquisition machine. The pattern of lean, AI-assisted operations running behind high-revenue consumer products is showing up repeatedly in bootstrapped founder stories right now, and Journalable is a clean example of it.
6. What I Learned From This Startup Story
What I Learned From This Startup Story
The detail most people will skip over is the $500,000 in Google Ads spend. That sounds like a lot until you realize it generated nearly the same amount in directly attributable revenue. The real money — the actual profit — came from subscribers who renewed, referred friends, and kept paying month after month. The ads weren't building revenue. They were building a subscriber base. The revenue came from that base compounding over time. That is a fundamentally different mental model for how paid acquisition works, and most first-time founders miss it entirely.
The deeper insight is that Steve's Android decision wasn't contrarian bravado. It was cost accounting. He didn't have money to waste on a platform with four times the CPM for a 20% conversion advantage. Bootstrapped founders who default to iOS because "that's where the money is" are often making a choice that is correct for funded companies with customer acquisition budgets — and wrong for their actual situation. Following the conventional wisdom of funded founders when you have no funding is one of the more common and least discussed reasons early-stage apps fail to gain traction.
What makes me skeptical: Steve's model works well in a high-volume, high-retention category like health and fitness, where users have strong personal motivation to keep tracking. The playbook — break-even acquisition, profit from renewals — depends on retention being good. If your app category has inherently high churn, the math stops working. The RevenueCat 2026 data shows AI-powered apps generate 41% more revenue per payer but retain subscribers at a meaningfully lower rate than non-AI apps. Journalable is an AI app in a high-retention category. That combination is the exception, not the rule.
The honest verdict: the Android opportunity is real and the Google Ads system is replicable. But the only thing Steve did that isn't in the playbook — and the thing that actually made the playbook work — is that he built something simple enough that people kept using it. No acquisition system saves a leaky product. The six steps are meaningless without step zero: build something people don't immediately abandon.
Key Takeaways
- Journalable went from under $1,000/month to $100,000+/month in under 18 months — bootstrapped, no external funding.
- 80% of revenue comes from Android. The iOS revenue is largely a free byproduct of Android ad campaigns.
- iOS CPM is roughly 4x Android CPM, but conversion rates are only ~20% better. For capital-constrained founders, Android's math is more favorable.
- The Google Ads playbook has six stages: attribution → install campaigns → asset optimization → tCPA campaign → budget scaling → product conversion optimization.
- A tCPA campaign requires a daily budget of at least 10x the target CPA to function properly.
- RevenueCat's 2026 data confirms iOS accounts for 77% of new subscription app launches — meaning Android is getting relatively less crowded, not more.
- The total fixed operational tool spend is under $450/month for a ~$1M ARR business.
- Steve's biggest regret: not starting to document and create content earlier. Distribution skills compound over time.
Frequently Asked Questions
Is Journalable still available on the Google Play Store?
Yes. As of the time of this article, Journalable is listed on the Google Play Store with close to one million downloads on Android. It operates as a premium subscription app with monthly and annual plan options.
How much does it cost to start a Google Ads App Campaign for an Android app?
You can start with as little as $10 to $15 per day for initial install campaigns. However, once you move to a Target CPA campaign, your daily budget must be at least 10 times your target cost-per-acquisition event. If your target CPA is $15, you need $150 per day minimum for the campaign to optimize properly.
Why does running Android Google Ads sometimes generate iOS installs?
Google App Campaigns serve ads across Google's entire network — including Google Search, YouTube, the Discover feed, and the Play Store. Some users who see Android-targeted ads may be iOS users who search for the app separately and find it on the App Store. This spillover effect means Android ad spend can drive a modest amount of iOS revenue without any direct iOS advertising cost.
What is the RevenueCat State of Subscription Apps report?
RevenueCat publishes an annual report benchmarking subscription app performance across iOS, Android, and web. The 2026 edition analyzed data from over 115,000 apps, covering more than $16 billion in revenue and over one billion transactions. It is one of the most data-rich public resources available for mobile app founders and is freely accessible on RevenueCat's website.
Does the Android-first strategy work for all app categories?
Not necessarily. The strategy is most effective in categories with strong user retention and high subscription renewal rates — health and fitness, productivity, and utility apps are good examples. In categories with inherently high churn, the break-even acquisition model Steve uses may not hold. Additionally, certain categories still have dramatically higher iOS revenue concentration, and localization strategy matters significantly when targeting non-North-American Android markets.
What did Steve say he would do differently if starting over?
His one clear regret: not building a content and documentation habit earlier. He spent close to a decade avoiding social media and has now found himself behind peers in content creation skills. His advice for anyone starting out is to document the journey publicly from day one — not because it will immediately drive installs, but because the skill of communicating your story compounds over time and becomes a significant distribution asset.
For more stories like this, the Chris Atkins car wash story covers a different kind of bootstrapped founder — one who went from a $45K salary to $860K a year in a completely offline business. The playbook is different, but the underlying discipline of following the data is identical.
Conclusion
Steve's story is well-documented, publicly verifiable, and genuinely instructive. The Android opportunity he identified is backed by real data from RevenueCat, not just founder intuition. The six-step Google Ads playbook he outlined is specific enough to actually use.
But here's the honest caveat: the Journalable case is easier to replicate in theory than in practice. Steve had two things working in his favor that aren't in any playbook — a genuine personal connection to the problem he was solving, and the discipline to keep the product ruthlessly simple even as revenue grew. Most founders add features when money comes in. Steve didn't. That decision kept his conversion rates high enough to make the entire ad system work.
Copy the playbook if it fits your situation. But don't mistake the tactics for the foundation. The foundation is a product people actually keep using. Without that, the six steps are just a more organized way to spend money.