The first monthly report for my first shipped app showed a few hundred yen in revenue. Downloads were ticking up every day; income wasn't. In all my years of indie development, that quiet number stung more than any build error ever did.
Rork has dramatically lowered the difficulty of building an app. But everything after the build—getting discovered, keeping users, converting attention into revenue—still comes down to human judgment and design.
This roadmap breaks the first year into four phases, with my own missteps folded into the reasoning: how to move from "I have an idea" to "I have revenue" using Rork.
Phase 0: Idea Validation (Weeks 1–2)
Three questions before you build
Who has what specific problem? Get to "people who [specific situation] struggle with [specific friction]." "An app for everyone" is an app for no one.
Does competition exist? Search the App Store. Zero competitors usually means no market. Competitors you can specifically beat on one dimension is a better sign.
Is there a revenue path? Advertising, paid download, IAP, or subscription—decide before building. The decision affects your feature set and user experience from day one.
Minimum validation
Rork's main advantage is speed. Use it for validation, not just building.
Week 1: Build only the core flow (1-2 screens) in Rork
Week 2: Show it to 5-10 target users, collect feedback
→ Decide: continue as-is, pivot, or stop
The order matters, and I'd argue it decides your first year: minimum thing → feedback → decision. Not: full build → launch → discover the assumption was wrong.
Phase 1: MVP Build and Store Launch (Weeks 2–8)
Pick a Rork plan by whether it gets you to "shipped"
The first budgeting question is which Rork plan to pay for. The free tier gives you 35 credits per month (up to 5 per day), resetting on the 1st with no rollover—enough to get a feel for the tool and build simple prototypes.
Junior ($25/month) covers idea validation and demos; Senior ($100/month) is the realistic line for building out an MVP; Rork Max ($200/month) adds native Swift output. The single test I use: does this plan get me all the way to shipped—actually live on the store? Time spent grinding on a plan that can't reach shipping is expensive even when the plan is free.
One more consequence of no rollover: "experiment early in the month, polish at the end" doesn't fit the credit model. Splitting your credits into weekly budgets and spending each week's share produces less rework. For a detailed break-even comparison across plans, see an honest comparison of Rork's pricing plans.
Building efficiently with Rork
Write prompts per screen, not per app: "Task list screen. Each task has a completion checkbox and delete button. Completed tasks show strikethrough." beats "Build me a task management app."
Complete the core flow first: The path users take most often (e.g., search → detail → purchase). Everything else is secondary features added later.
Supabase for data management: Works well with Rork. Authentication, database, and file storage in one place. The free tier handles indie app scale comfortably.
App Store and Google Play setup
The Apple Developer Program costs $99/year; Google Play charges a one-time $25 registration fee. First-year total: roughly $124. I treat this as a business expense you'll recover.
Required for App Store Connect: screenshots (6.7" and 5.5" sizes), app icon, privacy policy URL, description (up to 4,000 characters).
Required for Google Play Console: screenshots, feature graphic (1024×500px), description. If your submission gets rejected, the recovery process is covered separately in surviving an App Store rejection.
ASO basics that actually matter
ASO is where pre-launch time pays off most.
Title: Include your primary keyword. Under 30 characters. Format: "AppName - Core Benefit" (e.g., "FocusTimer - Pomodoro Clock").
Subtitle (iOS): 30 characters. Keywords you couldn't fit in the title plus a secondary value proposition.
Keyword field (iOS): 100 characters, comma-separated. No overlap with title or subtitle—those are already indexed.
Screenshots: Screenshot 1 is the most important. Communicate the core value visually. Add text captions—they measurably improve conversion.
Phase 2: Early Growth (Months 2–6)
Launch distribution tactics
Product Hunt: Effective for tech audience exposure. Aim for Top 5 on your launch day. Monday–Thursday submissions perform better. Time for US morning hours.
Reddit: r/apple, r/androidapps, relevant niche subreddits. Lead with value to the community, mention the app naturally. Pure self-promotion gets removed.
Build in public: Posting your development journey on Twitter/X or note.com (in Japan). You build an audience before launch, and the launch gets distribution from followers who watched you build it. The #buildinpublic community is genuinely receptive to this.
Choosing your monetization model
Advertising (AdMob) fits when:
- The app is used briefly, multiple times per day (utilities, tools)
- High download volume is achievable in your category
- DAU of 10,000+ makes ad revenue meaningful
Implementation timing: wait until 100 DAU. Before that, optimize for experience over revenue.
Rough eCPM reference (Japan/US):
- Banner: $0.50–2 / $1–4
- Interstitial: $3–15 / $8–25
- Rewarded: $5–30 / $15–50
Ad format selection and mediation setup are covered in more depth in an AdMob monetization strategy for Rork apps.
In-app purchases fit when:
- There's a clear "I want more of this" motivation (games, content, editors)
- Conversion rate target: 1–5% of DAU
For Rork apps, IAP implementation uses expo-in-app-purchases or react-native-iap. Purchase validation backend works well with Supabase Edge Functions.
Subscriptions fit when:
- Continuous value delivery (sync, content updates, ongoing AI features)
- You want predictable MRR for planning
- You can manage and reduce churn over time
Common indie pattern: start with ads or IAP to validate willingness to pay, then introduce subscription as the "serious user" option once you've confirmed the value proposition. That's the order I followed myself—my first app started with ads only.
Phase 3: Scale and Retention (Months 6–12)
Retention metrics and what to do about them
If you have downloads but users aren't coming back:
Target retention rates:
- D1 (next day): 30–40% is passing
- D7 (one week): 20–25% target
- D30 (one month): 10–15% target
Below these numbers, the most common causes are:
- Weak onboarding: User doesn't experience core value in first session
- Weak core loop: No reason to return
- Notification design problems: Permission not requested at the right time, or notifications aren't actionable
Push notification strategy: Ask for permission after the user has experienced value—not at launch. "You completed your first task! Enable notifications to stay on track?" outperforms "Allow notifications?" on the first screen.
Notification content needs a "reason to open now." "You have things to do" gets ignored. "You're 2 tasks from your daily goal" gets opened.
Review management
Target 4.0+ average rating. It directly affects App Store ranking.
When to ask for reviews:
✓ Immediately after the user solves their problem
✓ After 5+ sessions
✓ After a positive in-app achievement
✗ On first launch
✗ After an error or problem
Responding to negative reviews: Reply within 24–48 hours. "We're sorry for the inconvenience. This is fixed in version X.X" converts some reviewers and signals to future users that you're responsive.
Year-one revenue benchmarks (rough reference)
These vary enormously by category and execution:
500–2,000 downloads/month sustained: Ad revenue typically $50–500/month depending on DAU and engagement.
3,000–10,000 downloads/month: AdMob + IAP combination can reach $500–5,000/month range in high-value categories.
Reaching these numbers depends heavily on category selection and ASO quality. "Can I rank in the top 10 for a search term people actually use?" is the core question.
What to measure at the end of year one
The pattern I keep seeing in indie developers who make year-one revenue work: they solve one problem well. Not many problems adequately. One problem well.
I'd also suggest not making absolute revenue your only yardstick. Do you have one app that gets opened again the next day? Can you picture the face of even one user behind the numbers? If so, your second year has plenty of room to grow.
Start this week: write down your answers to the three Phase 0 questions. I hope this roadmap helps carry you through the first year.