From Rork to $1,000/month with AdMob — A Practical Indie Developer's Monetization Playbook

Four traits of apps that hit $1,000/month

A pattern I have seen consistently in apps that produce real AdMob revenue.

DAU above 3,000

AdMob eCPM (revenue per 1,000 ad impressions) varies by category and country, but $2-$5 is typical. With three to five ad views per user per day, $1,000 monthly revenue requires daily active users in the 3,000-5,000 range. That implies cumulative downloads of 50K-100K and monthly actives of 15K-30K.

D7 retention above 20%

The percentage of users who still use the app a week after install. Below 20%, you bleed users faster than you can acquire them, and you end up paying for installs to keep the AdMob revenue flowing — which usually wipes out the AdMob revenue.

The leverage point for D7 retention is the first session: deliver value within 30 seconds, and surface something fresh on the second open.

Multi-language including English

The Japanese market has middle-of-the-pack AdMob eCPM globally. US and Western European users carry eCPMs two to three times higher. Shipping with English on day one is much easier than retrofitting it; build that into the Rork prototype from the start.

Tracking permission design

Since iOS 14, users denying the App Tracking Transparency prompt cuts AdMob revenue substantially. A well-written usage description string and considered prompt timing materially raise opt-in rates.

Implementing AdMob in a Rork app

The mechanics, in order.

Install

npx expo install react-native-google-mobile-ads

Configure app.json:

{
  "expo": {
    "plugins": [
      [
        "react-native-google-mobile-ads",
        {
          "androidAppId": "ca-app-pub-XXXXXXXXXX~YYYYYYYYYY",
          "iosAppId": "ca-app-pub-XXXXXXXXXX~YYYYYYYYYY"
        }
      ]
    ]
  }
}

Banner

import { BannerAd, BannerAdSize } from "react-native-google-mobile-ads";
 
function HomeScreen() {
  return (
    <View style={{ flex: 1 }}>
      <ContentArea />
      <BannerAd
        unitId="ca-app-pub-XXXX/YYYY"
        size={BannerAdSize.ANCHORED_ADAPTIVE_BANNER}
      />
    </View>
  );
}

The ANCHORED_ADAPTIVE_BANNER automatically sizes to the device, which has consistently outperformed fixed-size banners in my testing.

Interstitial

import { InterstitialAd, AdEventType } from "react-native-google-mobile-ads";
 
const interstitial = InterstitialAd.createForAdRequest("ca-app-pub-XXXX/ZZZZ");
 
useEffect(() => { interstitial.load(); }, []);
 
function showInterstitialOnAction() {
  if (interstitial.loaded) {
    interstitial.show();
    interstitial.load(); // preload next
  }
}

Interstitials work well at natural transition points. Frequency matters — once every three to five user actions is the upper bound. More than that and uninstall rates climb sharply.

Rewarded

import { RewardedAd, RewardedAdEventType } from "react-native-google-mobile-ads";
 
const rewarded = RewardedAd.createForAdRequest("ca-app-pub-XXXX/WWWW");
 
rewarded.addAdEventListener(RewardedAdEventType.EARNED_REWARD, (reward) => {
  unlockPremiumContent();
});

User-initiated, rewarded with content unlock or extra functionality. Highest eCPM of any ad format (often two to three times banner) and lowest UX cost because the user opts in.

Ad placement patterns that work

Three patterns from production apps.

Pattern A — Launch interstitial + persistent banner

Simple. One interstitial on cold launch, a banner pinned on the main screen. Modest revenue per user but trivial to implement; good for first launch.

Pattern B — Action-completion interstitial + rewarded unlock

Strong fit for casual games and puzzles. Interstitial after a level clear; rewarded video for hints, lives, or skip. Roughly 1.5x to 2x the revenue of Pattern A.

Pattern C — Native ads inside content lists

Strong fit for content browsers and curation apps. A native ad every five to seven content items in the list. CTR runs higher than display formats; revenue often two to three times other patterns.

The combination of B + C tends to maximize per-user revenue. Designing those ad slots into the layout from the Rork prototype stage is much smoother than retrofitting them.

Why a portfolio beats chasing a hit

Trying to build one app to $1,000/month is harder than building five apps that average $200/month each. Three reasons indie developers should build portfolios.

Risk diversification

Apple or Google policy changes, store removals, sudden competitor launches — single-app dependency is fragile. Ten apps spread the risk.

Compounded learning

Building ten apps teaches you which categories, ad placements, and ASO tactics actually move the needle. Building one app leaves you guessing whether success was repeatable or lucky.

Rork makes volume realistic

One to two weeks of focused weekend work per app. Six to twelve apps a year is achievable solo. A portfolio that scale generates resilient income.

My own portfolio leans heavily into wallpapers, ambient/calming content, and lifestyle apps. No individual app is the breadwinner; together they form a steady base.

ASO basics you cannot skip

Building the app is half the work. Being found in the store is the other half.

Keyword selection

iOS App Store Connect gives you a 100-character keyword field. Generic terms ("game," "tool") have brutal competition. Find narrow terms with real volume:

• App Store Connect Analytics for your existing apps' search traffic
• Sensor Tower for category-level data
• AppTweak for deeper analysis when needed

Screenshots are the actual ad

Store screenshots are the conversion engine. Use text-overlay screenshots that explain what the app does in seconds.

My five-shot template:

1. The single most important experience + a short tagline
2. Main features in one frame
3. The differentiator vs. competitors
4. A user voice / review excerpt
5. Pricing model clarity (free with ads / IAP available)

Reviews matter

Store rating directly affects both ranking and conversion. In-app review prompts at the right moment dramatically improve rating volume.

import * as StoreReview from "expo-store-review";
 
useEffect(() => {
  if (sessionCount === 5 && positiveSignal) {
    StoreReview.requestReview();
  }
}, [sessionCount]);

Apple's guideline limits prompts to three per year per user; spend them on moments when satisfaction is provably high.

Real numbers from my portfolio

Indicative figures from running multiple apps for years (US dollars, 2026 baseline).

eCPM by category (banner-equivalent):

• Wallpapers / calming content: $1.70-$2.70
• Puzzles / time-killers: $2.40-$4.00
• Utilities: $1.40-$2.40
• Light learning: $2.00-$3.40
• Rewarded video: $7-$17 across all categories

Country-level eCPM differences (banner):

• US: $5.50-$8.00 (~3x Japan)
• Western Europe: $4-$6
• Australia: $4.70-$6.70
• Southeast Asia: $0.55-$1.00
• India / South America: $0.35-$0.70

English-language support is the single highest-ROI internationalization move. Pure Southeast Asia volume rarely justifies its operational overhead.

Combining AdMob with other revenue streams

Pure AdMob has a ceiling. Pairing it with adjacent monetization lifts the totals materially.

Remove-ads in-app purchase

A $4.99 one-time purchase to remove ads. Two to five percent of users typically buy. On a 10K-DAU app, that is $200-$500 of additional monthly revenue.

Subscription for premium content

Lean-back content apps can sell premium wallpapers, sound packs, or guided sessions. Apple/Google take 15-30% of IAP, but the recurring base compounds.

Affiliate partnerships

Utility apps can recommend related products via Amazon Associates or local affiliate programs. Done with restraint, this fits the user's intent rather than interrupting it.

The combination tends to lift a $1,000-AdMob-only app to $2,000-$3,000 in total monthly revenue.

A 90-day plan to your first $1,000 of mobile revenue

Days 1-14: Pick three high-fit category candidates. Download the top 3-5 competitors in each. Identify the differentiator. Pick the most promising of the three. Build v1 in Rork.

Days 15-30: Integrate AdMob (banner + interstitial + rewarded). Ship in English and your local language. Polish screenshots and store copy. Submit to both stores.

Days 31-45: ASO iteration, review collection, initial DAU buildout. Begin app #2 in parallel.

Days 46-70: Apply learnings from app #1 (D7 retention, eCPM, friction points) to app #2. Begin app #3. Ship a major update to #1.

Days 71-90: Three apps live. Combined DAU 1,000-2,000. Monthly revenue in the low hundreds of dollars. Establish sustainable cadence for #4 onward.

Six months in, $1,000 monthly is a realistic line. I have personally watched solo developers reach $3,000-$5,000 monthly within twelve months on this trajectory.

Mistakes I have made you can skip

Three lessons from the receipts pile.

Stuffing in too many ads. The instinct to maximize impressions destroys retention. An app I shipped early in my career went from $300/month to $200/month after I dialed back ad frequency — and to $1,000/month six months later because retention recovered.

Chasing short-term eCPM. Forcing rewarded videos into flows that did not need them cratered ratings on one of my apps. Long-term revenue lives downstream of long-term trust.

Going for the home run. Spending months on one ambitious app rarely outperforms shipping six small ones in the same period. Even seasoned developers are bad at predicting which app will hit. Ship small, ship fast, learn, iterate.

What to do next

Today, pick one app you actually use that runs on AdMob. Note what works and what irritates you. That note becomes your design brief.

This weekend, build a small high-fit app in Rork and ship it. Holding a live app in the store changes how every subsequent decision feels.

What "compounding" looks like over twelve months

A point that is hard to feel until you have lived it. Indie app revenue does not grow linearly; it grows in steps that compound.

In year one of running a portfolio, the first app might earn $50/month, the second $80, the third $120. Months one through six look unimpressive in absolute terms.

The compounding kicks in for two reasons. First, the back catalog keeps earning while you build the next app. Second, each new app benefits from everything you learned in the previous ones — better ASO, better ad placement, better retention design. App number five reaches $200/month faster than app number one did.

By month twelve, with eight to ten live apps, the same effort pattern produces a monthly total well into four figures. The trajectory is what makes the model worth committing to; any single month in isolation can be discouraging.

This is also why I argue against treating one app as the bet. A single app at $500/month is fragile and its growth ceiling depends on a single product's life cycle. A portfolio at the same total is robust and has a structural growth path because every new release lifts the average.

A short note on tooling and operating discipline

A final operational thought. Running ten apps requires being honest about what each one is doing. The minimum infrastructure I run for every portfolio:

A spreadsheet (or Notion database) with one row per app: install count, current DAU, last 30-day revenue, last update date, top three improvement ideas. Updated weekly.

AdMob and App Store Connect dashboards bookmarked and checked at least every other day. Anomalies — a sudden drop in eCPM, a review average tilting down — get caught early when you check often.

A standing weekly hour blocked for "portfolio maintenance": small bug fixes, screenshot refreshes, rating prompt timing tweaks. It sounds boring; it is also where the long-term compound interest comes from.

The discipline is light. The cumulative effect is large. Solo developers who stay in this game for years are the ones who treat the portfolio as a system rather than a series of one-off launches.