Google Play Console KPI New App: Indie Developer Benchmarks

You published your first Android app. Google Play Console is open in front of you, every chart is a mystery, and the only benchmark you have is the number in your head that you made up before launch.

You’re not alone. Every week, developers post questions like “65 installs in 4 weeks. As I have absolutely no reference, is that good or bad?” on r/googleplayconsole. The answers they get range from brilliant to completely wrong.

This guide gives you real indie benchmarks, explains what each KPI actually measures, and tells you which numbers to care about in month one versus month six.

TL;DR

• 65 installs in 4 weeks for a cold organic launch is completely normal and not a failure signal
• Store listing conversion rate of 20–35% is solid for a new app with no review history
• DAU/MAU below 0.10 is a retention problem; below 0.05 means stop spending on user acquisition
• The “Compare to Peers” tab in Play Console is the most underused tool for context
• Acquisition report data is statistically noisy below 50 installs — don’t make decisions from it

What Metrics Should You Track After Launching an Android App?

Play Console surfaces dozens of numbers. Most of them don’t matter for a new app. Here’s what actually does:

Week 1–4 (Traction Phase)

• First-time installers — not “installs,” not “active installs” — first-time installers. This is the count of unique users who installed for the first time. The gap between installs and first-time installers reveals how many users reinstalled, which is a sign of engagement.
• Store listing conversion rate — the percentage of people who viewed your listing and tapped Install. This is your listing’s effectiveness, not your app’s quality.
• Acquisition channels — where traffic is coming from. For a cold launch with no marketing, this should be almost entirely “Google Play Search.”

Month 1–3 (Retention Phase)

• 30-day active devices — also called MAU (Monthly Active Users). Devices that opened your app at least once in the last 30 days.
• 1-day active devices — also called DAU. Opened your app in the last 24 hours.
• DAU/MAU ratio — the fraction of your monthly users who show up daily. This is your engagement quality signal.
• Uninstall rate — how many users removed your app in the first 30 days.

Month 3+ (Growth Phase)

• Ratings and review velocity — how fast your rating is growing and whether it’s stable.
• Search ranking — for your target keywords, tracked outside Play Console.
• Crash-free users rate — from Android Vitals.

Resist the urge to watch all of them at once. In month one, the only numbers that matter are first-time installers, conversion rate, and your top acquisition channel.

Real Indie Benchmarks: What the Numbers Actually Look Like

Stop comparing yourself to Spotify. Here’s what real indie developers are seeing from organic launches, sourced from r/googleplayconsole threads in 2026:

The meditation app developer put it well: “The app gets around 15 to 20 organic downloads per day which honestly feels surreal.” From an indie baseline, 15–20 organic installs per day without paid acquisition is genuinely strong performance.

What these numbers tell you:

• 65 installs in 4 weeks is not a failure. It’s a cold start. Most apps with no social media presence, no Product Hunt launch, and no paid acquisition land in the 50–150 install range for their first month.
• 600 installs in 3 months is solid. This is an app that’s getting organic discovery and has keyword traction.
• 750 installs in 2 months with consistent daily organic is excellent. This app has found its search niche.

The r/googleplayconsole community consensus on small sample sizes: “Focus on install volume first, retention isn’t meaningful at this sample size.” This matters. Don’t draw retention conclusions from 65 installs.

What Is a Good Conversion Rate for a Google Play Store Listing?

Your store listing conversion rate is in Play Console under Store performance > Store listing.

Benchmark ranges for new apps:

A new app with zero reviews will almost always convert below a comparable app with 50+ reviews. This is normal. Reviews add social proof that directly lifts conversion. An app going from 0 to 50 reviews typically sees a 10–20% lift in conversion rate.

One thing Play Console doesn’t make obvious: conversion rate is calculated from store listing visitors only, not from all search impressions. Someone who sees your app in search results but doesn’t click through to your listing is not counted in this denominator. Your click-through rate from search results to your listing is tracked separately under “Impression to store listing visitor” in the Store listing stats.

Watch both numbers. A low click-through rate means your icon or app name is weak in search results. A high click-through rate but low conversion means your screenshots or description are losing people.

How to Read Google Play Console Statistics

Play Console statistics are genuinely confusing if you don’t know what each metric is measuring. Here are the distinctions that trip up almost every new developer.

Installs vs. First-Time Installers vs. Active Installs

• Installs — total install events, including reinstalls by the same user
• First-time installers — unique users who installed your app for the first time in a period. This is what you want when measuring reach.
• Active installs — devices that currently have your app installed and haven’t uninstalled it

If your installs number is significantly higher than your first-time installers number, users are reinstalling. This is often a sign of a crash loop or a bug that forces users to reinstall to fix.

Acquisition Report: Why It Looks Weird

The Acquisition report shows where your users came from — Google Play Search, Direct (typed your package name), Google Play Explore, etc.

Here’s what Play Console doesn’t tell you: this data is sampled and modeled at low volumes. Below roughly 50 installs, the attribution percentages are statistically unreliable. You might see 100% of installs attributed to “Google Play Search” when actually some came from a link you shared. Don’t make strategic decisions based on acquisition data until you have at least a few hundred installs.

The “User Acquisition” vs. “Retain and Earn” Sections

Play Console’s navigation splits into acquisition-focused reports and retention-focused reports. New developers often miss the retention section entirely. It lives under Grow > Store performance for acquisition and Grow > Statistics for retention.

The retention data you want: 1-day retention, 7-day retention, 30-day retention. These tell you what fraction of users who installed on a given day still had your app open after 1, 7, and 30 days.

How Many Downloads Should a New App Get in Its First Week?

Bluntly: there’s no meaningful universal benchmark because it depends entirely on whether you have an existing audience, any paid acquisition, or organic keyword ranking.

With no marketing, no existing audience, and fresh keyword ranking:

• Week 1: 0–10 installs is typical. Google takes time to index new apps.
• Week 2–3: 5–20 installs per week if your ASO is reasonable.
• Month 1 total: 30–150 installs for a solid cold organic launch.

With a Reddit or ProductHunt launch:

• Launch week spike: 50–500 installs depending on traction.
• Week 2 drop-off: typically 80–90% decrease from launch peak.
• Organic baseline after launch: back to the 5–20/week range unless ASO kicks in.

The task manager developer whose post hit a score of 26 upvotes noted this pattern clearly. Launch buzz creates a spike. Sustainable organic ASO creates the baseline that actually matters three months later.

What this means practically: Don’t measure your app’s potential by week-one downloads. Measure it by whether downloads are growing week-over-week at the 4–8 week mark. Flat is fine early. Growing is what you want.

What Does “Compare to Peers” Show in Play Console?

The “Compare to peers” tab is one of Play Console’s most useful features and one of its most ignored. You’ll find it in the Statistics section.

It shows how your app’s metrics compare to the median and top-quartile performance of apps in your same category. The comparisons include:

• Crash-free users rate
• ANR rate (App Not Responding)
• Average rating
• Rating volume

What it does not show: install counts, revenue, or DAU/MAU comparisons. Those are considered too competitively sensitive.

How to use it: Check your crash-free users rate against the category median. If you’re below median, you have a technical stability problem that’s suppressing your ranking. Play Console’s Android Vitals algorithm actively ranks stable apps above unstable ones. A crash-free rate below 99% puts you at risk of Play store policy flags.

The “Compare to peers” tab also helps calibrate whether a rating of 4.1 is strong or weak for your category. In some categories (games, tools), 4.1 is below average. In others (utilities, productivity), it’s above average.

Most developers discover this tab months after launch. Check it in week two.

DAU/MAU Ratio: What It Means for Your App

The DAU/MAU ratio is active users in a day divided by active users in a month. It measures how frequently your retained users come back.

General benchmarks by app category:

One developer reported 183 installs, 29 active devices, and a “user loss” rate of 1.25. Working through that: if 29 devices are active from 183 installs, that’s a 15.8% 30-day retention rate. For a cold launch with no onboarding optimization, that’s within normal range — but it’s a signal to improve onboarding before scaling acquisition.

The critical rule: if your DAU/MAU is below 0.10 and your 30-day retention is below 20%, do not run paid user acquisition. You will acquire users and watch them leave. Fix retention first. Every acquisition dollar spent into a leaky bucket accelerates your burn without building a sustainable user base.

The fitness app developer with 65 installs, 47 active devices, and 5 DAU had a DAU/MAU of roughly 0.13. For a fitness app with a small sample, that’s a reasonable signal — people are returning.

Indie Android App Growth: The Organic Acquisition Report

For most indie apps launching without a budget, organic search is your only realistic acquisition channel. Here’s how to read the acquisition report honestly.

What “organic” means in Play Console: Play Console attributes installs to “Google Play Search” when a user found your app by searching in the Play Store. It attributes installs to “Google Play Explore” for browse-based discovery (featured sections, similar apps).

The channel reality for cold launches:

• 80–95% of early installs will be “Google Play Search”
• 5–15% may be “Direct” if you shared a link
• “Explore” traffic is near-zero until you have enough velocity to appear in “Similar apps” sections

To grow organic search installs, you need keyword traction. That means your title, short description, and long description need to include the phrases users actually search. Google Play uses these fields as your primary keyword signals.

One developer whose 100 downloads came almost entirely from organic said: “Almost all installs came organically through ASO/search visibility.” That’s the goal state. When organic kicks in, it compounds. Each install generates usage signals that improve your ranking for relevant queries, which brings more installs.

The SEO effect in Play Store takes 4–8 weeks to show meaningful movement. Don’t measure keyword performance before the 6-week mark.

FAQ

What metrics should I track after launching an Android app?

In the first month: first-time installers, store listing conversion rate, and your primary acquisition channel. After month two: 30-day retention rate and DAU/MAU ratio. After month three: keyword ranking movement and review velocity. Most first-time developers track too many metrics too early and draw wrong conclusions from noise.

What is a good conversion rate for a Google Play store listing?

25–40% is solid for a new app. Below 15% means your icon, screenshots, or short description need work. Your conversion rate will be lower than comparable apps with reviews because social proof directly lifts the number. The jump from 0 reviews to 50 reviews typically adds 10–20 percentage points.

How do I read Google Play Console statistics?

The key distinction is “first-time installers” (unique new users) vs. “installs” (total events including reinstalls). Use Statistics for retention data and Store performance for conversion data. The Acquisition report is unreliable below 50 installs — it uses sampling and modeling. Don’t make strategic decisions from it at low volumes.

How many downloads should a new app get in its first week?

With no paid acquisition and no existing audience: 0–10 in week one is completely normal. Google needs time to index your app. The benchmark that actually matters is week-4 to week-8 growth rate. If you’re growing week-over-week at the one-month mark, your ASO is working.

What does “Compare to Peers” show in Play Console?

It shows how your app’s crash-free users rate, ANR rate, average rating, and rating volume compare to the median and top-quartile apps in your category. It does not show install or revenue comparisons. Use it primarily to benchmark your technical stability against category norms. If you’re below the crash-free users median, that’s your first priority to fix.

Should I be worried if my DAU/MAU ratio is low in the first month?

Only if you have a large enough sample to draw conclusions. Below 50 active users, DAU/MAU is noise. Above 100 active users and below 0.10 DAU/MAU, yes — that’s a retention problem worth investigating. The fix is almost always onboarding: users who don’t form a habit in the first three sessions rarely return.

The Only Benchmark That Actually Matters

Developers get obsessed with week-one download counts. Experienced ones watch the 60-day install curve.

If your installs are growing week-over-week at the 6-week mark, your app has found keyword traction. If they’re flat, your ASO needs work. If they dropped off after a launch spike and never recovered, you’re relying on promotion that you can’t sustain.

Getting out of the launch mindset and into the growth mindset takes time. One developer in the r/googleplayconsole community gave the best reframe for new Android developers: “Get out of your coder shoes and you’ll see a whole new world.” That world has retention curves, keyword research, and store listing optimization as its core languages.

The numbers in your Play Console tell a story. Learn to read it on its own terms.

Growing an Android app and want to accelerate your review velocity? ExtensionBooster helps indie developers build authentic review momentum that drives Google Play ranking and organic installs.