• Competitors
  • Store Data
  • Mobile apps
  • Ratings
  • Releases

App competitor analysis: a step-by-step guide with free data

App competitor analysis step by step: pick rivals, compare ratings, releases and reviews on the App Store and Google Play with free data, then automate it.

Author
Extenify Team
Published
Reading time
13 min read
Wooden chess pieces standing on top of a smartphone that lies on bright green artificial grass

App competitor analysis is the habit of checking what the apps you compete with are doing in the stores: how often they ship, how their ratings move, what their users complain about and how they change their listings. Most guides on page one treat it as a one-off ASO audit inside a paid tool. This guide treats it as a monitoring job you can start today with free public data from the App Store and Google Play, using a real competitor set we checked on October 29, 2026, and a short script that turns it into a daily record.

Key takeaways

  • Start with 5 to 10 competitors and record their store IDs: the App Store ID, the bundle ID and the Google Play package name.
  • Four public signals carry most of the value: release cadence, ratings and rating counts per store, review themes, and listing changes.
  • In a set of seven habit tracker apps, release cadence ranged from more than 25 releases in 90 days to none since March. That gap says more about a competitor's momentum than its rating does.
  • The same app can rate very differently per store: Routinery had 4.71 on the US App Store and 4.4 on Google Play on the same day.
  • Single readings mislead. Apple's search endpoint returned an older version than the product page for three of the seven apps, so record a daily snapshot and compare trends.

What app competitor analysis should answer

A useful competitor review answers a handful of concrete questions rather than producing a slide of logos:

  • Who is gaining users, and how fast? Rating counts on the App Store and download figures on Google Play are the public proxies.
  • How actively is each competitor building? Release dates and release notes show who ships weekly and who has stalled.
  • What do their users love and hate? Reviews tell you which features to match and which complaints you can win on.
  • What are they testing in the store? Changes to names, subtitles, screenshots and prices are visible to anyone who looks every day.

Keep those four questions in mind and every number below has a purpose. If a metric does not change a decision about your roadmap, your listing or your pricing, you can stop tracking it.

Step 1: Build your competitor set

The AppFollow team's competitor analysis guide splits competitors into direct, keyword, category and regional rivals, and that split works well in practice:

  1. Direct competitors solve the same problem for the same user. These are the apps people compare you with in reviews.
  2. Keyword competitors rank for the searches you want, even if their product is different.
  3. Category leaders set expectations for design, pricing and update frequency.
  4. Regional competitors matter if you sell in markets where local apps lead.

Five to ten apps is enough. For each one, write down the identifiers you need to fetch data:

Store Identifier Where to find it
App Store Numeric app ID The id1528595748 part of the product page URL
App Store Bundle ID The bundleId field of an iTunes Search API lookup
Google Play Package name The id= parameter of the listing URL, such as com.finch.finch

An app often has a different name on each store, and some competitors exist on only one. Record what exists rather than assuming parity: for the seven apps in our example below, we tried the likely package names for four on Google Play and found listings for two.

Step 2: Collect the public numbers

Both stores expose enough data for a solid comparison without any paid tool:

Signal App Store Google Play
Rating and rating count iTunes Search API, per country Listing page (rating and review count)
Current version and date iTunes Search API, product page "Updated on" date, version when the listing shows one
Release history Last 25 versions on the product page Not shown; record it yourself
Size of the user base Rating count as a proxy Download bucket and a more precise undocumented figure
Reviews Product page and RSS feed Listing page shows a sample
Price and in-app purchases Lookup fields and product page Listing page

Two details matter here. App Store ratings belong to each country's storefront, so always record the country you read. And Google Play has no public version history, which our guide to Google Play version history covers in depth. For the size of a competitor's Android user base, see how the Google Play download count works and why its precise figure needs care.

Step 3: Compare release cadence

Release cadence is the most underrated competitor signal. A team that ships every week is fixing bugs, testing features and probably asking for ratings after good releases. A team that has not shipped in months is either finished or stuck.

We took the top seven results for "habit tracker" from the iTunes Search API in the US storefront and counted the releases each app's product page listed in the 90 days to October 29, 2026:

App Rating (US) Ratings Latest version Releases in 90 days
Finch: Self-Care Pet 4.95 769,130 3.73.233 (Oct 29) 25+
Habit Tracker 4.79 148,345 2.15.9 (Oct 29) 13
HabitKit 4.84 2,515 1.19.0 (Oct 27) 11
Routine Planner, Habit Tracker 4.71 18,134 3.30.5 (Oct 29) 10
Onrise: Habit Tracker & Focus 4.84 2,601 1.1.9 (Aug 25) 2
Habit Tracker - Daily Goals 4.85 3,467 1.1.1 (Oct 28) 1
Productive - Habit Tracker 4.60 91,070 3.26.39 (Mar 19) 0

Finch's 25 listed releases all fell within 78 days, and the App Store only shows the last 25, so its real count is higher. Our App Store version history guide explains that limit and how to keep a complete record.

What the table tells you:

  • Ratings barely separate these apps. Six of seven sit between 4.71 and 4.95. The rating alone would not tell you who is winning.
  • Cadence separates them clearly. Finch ships more than twice a week, three apps ship roughly every week or two, two have shipped once or twice in three months, and Productive has not shipped in over seven months despite a large rating count. That last one is either a stable cash cow or an opening for you; its recent reviews will tell you which.
  • Rating count is a size signal, not a quality signal. Finch has about 300 times more ratings than HabitKit, yet HabitKit ships almost as often as the much larger Habit Tracker.

Step 4: Compare ratings across stores and countries

Look at each competitor's rating in every store and every market you care about, not only the US App Store. On October 29, Routinery had a 4.71 average on the US App Store and 4.4 on Google Play, while Finch had 4.95 and 4.9. A gap like Routinery's usually means the Android app lags the iOS app in quality or features, which is worth knowing if Android is your stronger platform.

Track the rating count as well as the average. A sudden jump in new ratings after a release usually means the competitor added or changed a rating prompt. A falling average with a rising count means new users are less happy than old ones. Our guide to reading review and rating trends covers how to read both together, and Google Play's per-country and per-device rules are explained in our Google Play rating calculation guide.

Step 5: Read competitor reviews for gaps

Competitor reviews are free product research. Read the most recent one-star and two-star reviews for each app and sort complaints into a few buckets: bugs, missing features, pricing, sync and data loss, and support. Then read the five-star reviews for what users praise, which tells you what you must match.

Three habits make this work:

  • Read by version. Reviews posted right after a release often describe what that release broke. Line them up with the release dates you collected in step 3.
  • Count themes, do not collect quotes. "Fourteen reviews about sync failures in October" is a finding; one angry quote is an anecdote.
  • Automate the labeling once the set grows. Our app review analysis with an LLM guide shows how to label reviews from every store with a fixed taxonomy for well under a dollar per 10,000 reviews.

Step 6: Watch listing changes

Competitors run experiments in public. When an app changes its subtitle, swaps its first screenshot, changes its price or rewrites its "What's new" text, that change is a hypothesis they are testing. Record the listing fields each day and diff them, and you will see:

  • name and subtitle changes, which reveal keyword targeting;
  • price and in-app purchase changes, which reveal monetization tests;
  • release notes, which reveal what they think users care about;
  • new markets, when an app appears in a storefront where it was not available.

You do not need to copy any of it. The value is in knowing what the market is trying before your users ask why you have not.

Automate app competitor analysis with a daily snapshot

A spreadsheet works for one quarterly review. Monitoring needs a daily record, because store data is noisy and cached. When we collected the table above, Apple's search endpoint returned version 2.15.8 for Habit Tracker while its product page already showed 2.15.9, released hours earlier, and Finch and Routinery showed the same lag. A lookup by ID a little later returned the new versions. One reading can be a day stale; a daily series is not.

This Node.js script records one row per app, store and day from the iTunes Search API and the public Google Play listing:

// competitor-snapshot.mjs: one row per app, store and day from free public store data.
// Node.js 18+. Run once a day; keep the output (a database table or a JSON file) as your history.
const COMPETITORS = [
  { name: 'Finch', appStoreId: 1528595748, playId: 'com.finch.finch' },
  { name: 'Routinery', appStoreId: 1450486923, playId: 'com.alt.goodmorning' },
  { name: 'HabitKit', appStoreId: 6443918070 },
];
const UA = { 'user-agent': 'Mozilla/5.0 (compatible; store-stats-check)' };
const day = new Date().toISOString().slice(0, 10);

async function appStore(ids, country = 'us') {
  const res = await fetch(`https://itunes.apple.com/lookup?id=${ids.join(',')}&country=${country}`);
  if (!res.ok) throw new Error(`iTunes lookup failed: ${res.status}`);
  return (await res.json()).results.map((a) => ({
    store: 'app-store', id: String(a.trackId), day,
    rating: a.averageUserRating, ratings: a.userRatingCount,
    version: a.version, versionDate: a.currentVersionReleaseDate?.slice(0, 10), price: a.price,
  }));
}

async function googlePlay(packageName) {
  const res = await fetch(`https://play.google.com/store/apps/details?id=${packageName}&hl=en_US&gl=US`, { headers: UA });
  if (!res.ok) return null;
  const html = await res.text();
  const updated = html.match(/Updated on<\/div><div[^>]*>([^<]+)</)?.[1];
  return {
    store: 'google-play', id: packageName, day,
    rating: Number(html.match(/aria-label="Rated ([0-9.]+) stars/)?.[1]) || null,
    installs: html.match(/\["[\d,]+\+",\d+,(\d+),"[^"]+"\]/)?.[1] ?? null, // undocumented figure
    versionDate: updated ? new Date(`${updated} UTC`).toISOString().slice(0, 10) : null,
  };
}

const rows = await appStore(COMPETITORS.map((c) => c.appStoreId));
for (const c of COMPETITORS.filter((c) => c.playId)) {
  rows.push(await googlePlay(c.playId));
  await new Promise((r) => setTimeout(r, 2000)); // be gentle: one listing every 2 seconds
}
console.table(rows.filter(Boolean));

On October 29 it returned Finch at 4.947 with 769,209 ratings and version 3.73.233 on the App Store, and a 4.9 rating, an "Updated on" date of October 29 and an undocumented install figure of about 16.5 million on Google Play. The Google Play part reads an undocumented page, not an API, so keep the volume low, cache results, back off on HTTP 429 and expect to update the patterns if Google changes the page.

To make it a real monitor:

  1. Schedule it once a day. Our Node.js cron job guide shows how to run a daily job exactly once and catch up after downtime.
  2. Store one row per app, store and day. A table keyed on those three columns is enough; the PostgreSQL time series guide covers idempotent writes and 7-day growth rates.
  3. Alert on changes, not on values. A new version, a rating move of more than 0.05, a jump in rating count or a price change are the events worth a message. Our guide to store change alerts your team will actually read explains how to keep that list short.

A weekly competitor scorecard

Once the data is flowing, a weekly scorecard keeps the analysis honest. One row per competitor:

Competitor Releases this week Rating change (per store) New ratings Review themes Listing changes
Competitor A 2 App Store +0.01, Play 0.00 +1,900 Sync bugs after 3.4 New subtitle
Competitor B 0 App Store -0.03 +40 Pricing complaints Price up

Add one line at the bottom: what you will do differently because of it. If the answer is "nothing" for several weeks, trim the scorecard. The same structure works for your own app, which is why we recommend tracking yourself in the same table as your rivals; our Chrome extension metrics scorecard follows the same idea for browser extensions.

Mistakes to avoid

  • Copying features because a competitor shipped them. A release tells you what they tried, not whether it worked. Watch their ratings and reviews for two or three weeks after a release before reacting.
  • Comparing one store with another. A 4.4 on Google Play and a 4.7 on the App Store are not directly comparable audiences. Compare each competitor with you in the same store and country.
  • Trusting one reading. Cached endpoints, staged rollouts and per-country ratings all make single numbers unreliable. Trends over weeks are what matter.
  • Tracking too many apps. Ten well-chosen competitors you actually review beat fifty you never look at.

Track competitors without maintaining scripts

The script above is a good start, but it needs a scheduler, storage, per-country handling and fixes whenever a store changes its pages. Extenify does that work for you. It is a unified dashboard for competitor app monitoring that records public store listing data for App Store and Google Play apps, plus Chrome, Edge and Firefox extensions, every day. It keeps the history of ratings, rating counts, installs and versions for your apps and your competitors side by side, and sends alerts to email, Slack, Telegram, Discord or Teams when something changes. Every plan starts with a 7-day free trial with no credit card required, and the pricing page shows how many apps each plan tracks. If you also build browser extensions, the same approach applies across stores, as our guide to tracking one extension across Chrome, Edge and Firefox shows.

Frequently asked questions

How do I do a competitor analysis for an app?

Pick 5 to 10 direct, keyword, category and regional competitors, record their store IDs, then compare four things in each store: release cadence, ratings and rating counts, review themes and listing changes. Repeat it weekly from a daily data record rather than doing it once.

What tools can I use for app competitor analysis?

Paid ASO platforms such as AppTweak, AppFollow, Sensor Tower and Appfigures add estimates for downloads, revenue and keyword rankings. For ratings, versions, release dates and listing changes, free public data is enough: the iTunes Search API, App Store product pages and Google Play listings.

Can I see how many downloads a competitor's app has?

On Google Play, every listing shows a download bucket such as "1M+", and the page holds a more precise undocumented figure. The App Store shows no download numbers, so the rating count is the usual public proxy for size.

How do I find my app's competitors?

Search the store for the keywords you want to rank for, note the apps that appear in the top results, check the "You might also like" and similar apps sections on your own listing, and read your reviews for apps users mention by name.

How often should I check competitor apps?

Collect data daily, because releases and ratings change daily and store data is cached. Review it weekly with a short scorecard, and do a deeper review of positioning and pricing once a quarter.

Is it okay to collect competitor data from the stores?

Ratings, versions, release notes and prices are public listing data. Use official endpoints such as the iTunes Search API where they exist, read pages at a low rate, cache results, and follow each store's terms. Never collect personal data from reviews beyond what you need.

Summary

App competitor analysis works best as monitoring, not as a yearly audit. Choose a small set of real competitors, record their IDs in each store, and compare release cadence, ratings per store and country, review themes and listing changes. In our habit tracker example, ratings barely separated seven apps while release cadence separated them sharply, and the same app rated 4.71 on one store and 4.4 on the other. Record a daily snapshot, alert only on meaningful changes, review a scorecard weekly, and act on the patterns rather than on any single number.

Image credits

Put every store in one dashboard tonight.

Sign in with Google, paste one store link, and your unified view is live in under a minute. Then 7 days of Pro free, no credit card required, and you never touch your app's code.

Start free trial