Loading page…
A cozy farming RPG earned a $5K+ month when App Store discovery lifted downloads and paying players followed.
nearly 600 iOS reviews · 4.7-star iOS rating
A good game can prove demand during a discovery spike; the durable business is the audience you keep after Apple stops sending traffic.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Simon Grimm moved from teaching React Native to building Tiny Harvest, a cozy mobile farming RPG he saw as a possible real business. The game was about six months old when he reported a month above $5,000 in revenue, after an earlier milestone of roughly $2,500. He had added two areas, including a blacksmith and an airport for orders, but says the major change was distribution: App Store browse traffic climbed, installations rose, and revenue followed. He describes a peak near 2,000 on the App Store Browse line, followed within days by a sharp drop. The game itself had not changed materially during that reversal. At the time of the update, Tiny Harvest was nearing 600 iOS reviews with a 4.7-star rating. Grimm's conclusion shifted from adding features toward marketing, onboarding, retention, and building channels he can influence. He plans to return to Reddit, test creator marketing, improve the store page, and keep shipping content.
A small mobile game needs its first customers where cozy-game players already compare screenshots, not through a broad launch blast. For Tiny Harvest, Simon's early Reddit posts brought users, and he later stopped after receiving negative feedback.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself. The exact words are quoted below, with a timestamp that jumps to the second each figure is said.
“Last month, my game made over $5,000. And I thought I had finally figured out everything until a few days later.”
0:00 · hear it in the videoData credibility: Simon, the developer, says the game made over $5,000 last month, up from about $2,500 two months earlier, and points to his RevenueCat dashboard and the App Store Connect browse graph on screen. The revenue figures are spoken by the founder about his own game, not shown as an audited statement, and he does not say whether they are gross or net of Apple's fee. The near-600 iOS reviews and 4.7-star rating are also his own report. No costs or profit are given.
For a cozy farming game like Tiny Harvest, make the first paid action feel like an extension of play: let the player enjoy a visible farm win before presenting something worth paying for.
An App Store browse wave and strong reviews created a temporary loop: Apple showed Tiny Harvest to more people, installs rose, more reviews arrived, and RevenueCat revenue rose with them.
A distribution dip is emotionally rough for an indie game because several days of lower traffic can make a successful month look like a false signal. Tiny Harvest has a useful anchor: players leave favorable reviews and spend in the game, while the browse source moves outside the developer's control.
Tiny Harvest is a cozy farming role-playing game built for iOS and Android. Players develop a farm, explore areas, collect gear, and take on orders. Grimm describes adding two areas since his prior revenue update, including a blacksmith and an airport, while keeping the underlying game largely the same through the App Store traffic spike. That distinction matters: a game can earn meaningful revenue without a large content update if existing players enjoy the loop and the store surfaces it to new people. The product already has a sizable review base for a young indie title, nearing 600 iOS reviews at 4.7 stars. For a small team, the practical product question is whether each new area deepens repeat play or merely increases the maintenance burden. Farm upgrades, short orders, seasonal events, and clear progression can support long-term engagement, but each should reinforce the comfortable pace that makes a cozy game appealing.
Our read: validate monetization instead of assuming a particular purchase mix or price point. The evidence is that players spend in Tiny Harvest and that revenue rose alongside installations during the App Store browse period. For a cozy farming RPG, preserve a generous core loop and sell convenience or expressive extras only when they add delight rather than block basic progress. Keep purchases optional, make value clear before checkout, and avoid designing a progression wall that damages reviews. Measure the first purchase rate, repeat purchases, refunds, and revenue per retained player by acquisition source. A one-month revenue high can come from a platform traffic burst; the healthier signal is whether players acquired through search or community channels return and continue paying. The business can grow more predictably when content cadence, onboarding, and monetization all serve the same player habit.
The creator describes using App Store Connect for acquisition analytics and RevenueCat for revenue reporting. Those tools make it possible to separate Apple's App Store Browse traffic from other discovery sources and see how downloads correspond to purchase activity. That is a useful minimum analytics setup for a mobile game: keep storefront reporting for installs and product-page behavior, and a cross-platform purchase layer for proceeds and refunds. The development stack, production costs, and operating margin are not part of the reported figures, so founders should avoid treating the $5K+ month as profit. Budget for ongoing art, music, testing across devices, support, and content updates before projecting cash flow. Keep a lightweight release process so bug fixes do not interrupt the game during a traffic spike. A solo developer can start with instrumentation and a clear release checklist, then add tools only when they answer a specific question about acquisition, retention, or monetization.
Copy the habit of showing the whole journey in public: Grimm reports milestones, explains what changed, and shares the discouraging reversal as clearly as the win. That can attract players, make the project memorable, and generate useful feedback without requiring a large advertising budget. Copy the focus on product quality too: reviews and willingness to spend suggest that players value the game, so protect the core loop while testing discovery. Change the assumption that feature work is always the highest-value task. Grimm estimates that about half of his time should go to marketing, onboarding, retention, and conversion; that is a useful operating prompt for a solo game developer. Build a game with a sharply defined cozy audience, measure where installs originate, and use short community and creator experiments to earn repeat discovery. Do not copy the dependence on one store's browse placement. Turn each surge into a chance to collect permission-based contacts and learn which players become regulars.
The clearest risk is platform concentration. App Store Browse sent Tiny Harvest a surge and then stopped, with the developer describing traffic falling close to its earlier baseline within days. A product can have positive reviews and still lose visibility if store algorithms change. A second risk is confusing a short revenue spike with a repeatable acquisition engine; the month above $5,000 came alongside unusually high installs, and the account gives no comparable long-term revenue series. Another risk is spending all available time on new areas while onboarding and store conversion remain weak. The game also needs enough content to retain players without making a solo developer's workload unmanageable. Build a mix of search optimization, community presence, creator discovery, and returning-player events. Track retention and purchase behavior by channel, and protect time for marketing alongside development. The upside remains attractive, but the durable asset is a returning player base rather than a temporary placement.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,403 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click