Publish a Rork Max app to the App Store and this moment arrives for almost every indie developer: 5 downloads on day one, 30 in the first week, 100 in the first month. And zero revenue. It isn't a crisis — it's the default outcome when you ship without preparing for monetization.
I have been shipping indie apps since 2014, and the first 30 days after launch quietly decide how long the app survives. This article is a practical checklist for the 30-day window, designed to put actual revenue on the board before you lose momentum.
A premise: monetization starts before launch, not after
The biggest framing mistake is "I'll think about monetization after the app is live." By then it is usually too late. Early users anchor on "free" and churn out as soon as you add a paywall later.
Three pieces must ship in the initial build: an AdMob banner, a paywall entry point (the actual purchase can come later), and usage tracking. With these three, you can adjust your monetization model quickly once data starts flowing.
Day 0 — final pre-launch check
Must-haves for the night before launch.
Specified Commercial Transactions disclosure, privacy policy, and terms of service accessible from inside the app or via linked web pages. Missing any of these gets you rejected.
Your App Store listing description must include at least one sentence of unique value that competitors don't claim. Generic phrasing like "a helpful app" gets buried in search. Rork apps tend to win when they lead with something concrete like "AI automates X."
Screenshots must communicate the core feature in under three seconds. The first one is overwhelmingly the most important. In my experience, screenshots with large text overlays convert 1.5-2× better than clean app captures.
Days 1-7 — line up three inbound channels
Do not rely on ASO for the first week. Search rankings take 2-4 weeks to settle. You manufacture inbound through active channels.
Channel 1: your own SNS (Instagram, X, Threads). Post three preview videos in 15s, 30s, and 60s versions, each tuned for the platform it targets.
Channel 2: funnels from your existing sites or apps. If you have any web presence, place a banner for the new app on the homepage. Existing users convert disproportionately.
Channel 3: communities where the target user already hangs out. Reddit, Discord, note, Zenn, Hacker News, or Product Hunt — pick the one that fits the app and post an intro.
The goal for week one is 50-100 downloads from these three channels. AdMob impressions start paying out at this point — usually a few dozen yen. That is your first dollar of revenue.
Days 8-14 — AdMob tuning and paywall verification
Week two is about starting to measure.
AdMob tuning checkpoints
Confirm your eCPM (revenue per thousand impressions) is visible in the dashboard. For Rork apps at launch, 0.70-2.00 USD is the normal range. An extreme low (under 0.40 USD) usually means a misconfigured ad unit or a poor user-demographic match.
Placement matters. A bottom-pinned banner is safe. Interstitials belong at natural screen transitions — never right after a user tap. Interstitials on a tap cause mis-taps, which spike short-term revenue but torch retention.
Paywall verification
If your build shipped with a paywall flow, run a real purchase yourself in week two. Confirm the purchase completion screen, the receipt email, the unlock, and the "restore purchases" path all work.
A bug I have been bitten by: the user's purchase state vanished after an app relaunch. In Rork Max, make sure you are subscribing to Transaction.currentEntitlements in StoreKit 2 correctly — not just checking once at purchase time.
Days 15-21 — convert your first paying users
Week three is when you actively manufacture paying users.
Tactic 1: usage-gated paywall
"Free up to 5 uses, paywall on use 6." Simple, explicit, fair. Show the purchase screen to any user who crosses three uses. In Rork Max, @State plus StoreKit 2 gets you there in a few dozen lines.
Tactic 2: A/B test price points
With the first few dozen users, test multiple price points in parallel. For example, 2.99 USD/month vs 9.99 USD one-time vs 19.99 USD one-time — randomly assigned per user. A week of data tells you which generates more revenue.
In my experience with consumer-facing Rork apps, a one-time 9.99 USD is usually the sweet spot. Monthly triggers "don't want to pay every month" resistance, high one-time triggers "can't judge without trying" resistance.
Tactic 3: launch discount
A 30% launch discount for the first 100 users. Scarcity drives conversion. StoreKit 2's Introductory Offer is the right implementation mechanism.
Days 22-30 — analyze and optimize
Week four is analysis week. Five numbers matter:
DAU, retention (day 1 and day 7 relaunch rate), AdMob eCPM, free-to-paid conversion rate, and ARPU (average revenue per user).
Log them to a spreadsheet daily. With Rork Max, you can connect App Store Connect API to pull this automatically — Apps Script writing daily rows into a Sheet gives you a weekend-ready dashboard.
Use the numbers to set next month's priority. Low retention → improve onboarding. Low free-to-paid → adjust paywall timing. Low eCPM → change ad format.
Realistic 30-day revenue
Following this checklist, expected 30-day outcomes:
- Downloads: 300-800
- DAU: 30-100
- Monthly ad revenue: 7-35 USD
- Monthly IAP revenue: 15-70 USD
- Total monthly revenue: 20-100 USD
Yes, that's modest. But it isn't zero — and "non-zero in month one" is the single best predictor of whether you'll keep improving the app. 1,000 USD/month typically needs 3-6 months of continued iteration from this starting base.
Next step
First-30-day revenue is a precondition for long-term success. Zero for three months, and most indie developers quietly abandon the app.
For stable 3,000 USD/month revenue, a multi-app portfolio strategy works better than chasing one breakout hit. I cover this in the Rork cross-platform revenue portfolio strategy. Diversifying across several apps matches indie-scale risk far better than betting everything on one.