Google Play Store (Web Catalog)

The storefront layer of Android, written down. Every app on Google Play resolves to a structured details page carrying its display title, developer, package ID, store category, star rating, review count, download bracket, content rating, ad and in-app-purchase flags, full "About this app" text, release and last-update dates, developer support contact and a similar-apps list - sixteen documented fields per record here, verified against live pages. Around the detail pages sit the curated surfaces: the APPLICATION category family and its subcategories, the GAME family, Editors' Choice rails and themed collections such as Government apps & citizen services.

Within Datadory's 25-dataset application-software pool, this is the live current-state view: 2M+ listings that move when the store moves, not a frozen archive. Get a sample of this dataset - name a category, a storefront country or a competitor set, and the matching rows come back first.

One app, one flat record. The anchor row of the sample set:

app_title         : Spotify: Music and Podcasts
developer_name    : Spotify AB
package_id        : com.spotify.music
category          : Music & Audio
rating            : 4.3
review_count      : 36.2M
downloads_bracket : 1B+
content_rating    : Teen
flags             : Contains ads | In-app purchases
updated_on        : Aug 18, 2026

Collection-level rows run lighter - a name and a rating against the rail they appeared in: ChatGPT at 4.8 and Duolingo: Language Lessons at 4.7 under Editors' Choice apps; DigiLocker at 4.2 and UMANG at 4.6 under Government apps & citizen services. Detail records carry the full sixteen columns; card records prove what the curated surfaces were showing.

Sixteen documented fields make up a record, with definitions marked verified against live listing pages - a standard met by 85.7% of the 1,744 datasets Datadory catalogs. Fourteen fields carry a worked example in the dictionary below. Two - privacy_policy_url and similar_apps - arrive populated on every record but without fixed examples, so they sit under additional fields on request together with derived columns such as exact rating histograms and the precise install counts standing behind the public brackets.

Geography - a global storefront with country and locale variants; rankings and featured collections differ by storefront country, so the same app presents differently market to market.

Temporal - a live current-state catalog. Per-app history is not retained by the store; the changelog carries only the latest version notes, so longitudinal reads come from captures repeated on a schedule.

Granularity - one record per app at detail level, plus curated collections and category listings at app-card level: two grains, joined by package ID.

API, files, or your warehouse. Daily, weekly, or hourly.

• Competitor tracking - watch rival Android apps' ratings, install brackets, changelog notes and similar-app placement per details page. It is the richest view of competitor Android listings in the pool, and one of 195 cataloged datasets serving competitor-tracking work.
• Market sizing - download brackets act as ready-made distribution bands; aggregate them across the APPLICATION and GAME families, per storefront country, to size segments without estimating from scratch.
• Diligence on mobile-first businesses - install brackets and rating trajectories visible on listing pages give investors a ground-truth read ahead of a data room.
• Shopping-app merchandising - e-commerce teams track competitors' review counts and release notes directly on their Play listings.

For cross-platform work, pair it with the Play and Apple App Store Metrics table (3,194,924 unified rows) or read the vs Apple iTunes Search API comparison for the iOS-side counterpart.

Ranked by relevance in Datadory's persona tagging:

1. Competitive Intelligence & Product Teams (relevance 3): ratings, install brackets, changelogs and screenshots per app page make this the baseline board for Android competitor watching - worked examples on our competitive intel teams page.
2. E-commerce Operators (relevance 2): track shopping-app competitors' ratings, review counts and changelog notes on their Play listings.
3. Sales & Growth Teams (relevance 1): check a prospect's Play presence, install bracket and review trajectory before outreach.
4. Investors & Quant Researchers (relevance 1): install brackets and rating trajectories inform diligence on mobile-first businesses.

Three honest gaps. First, scale: 2M+ live listings is a floor, not an official figure - Google publishes no count, and totals vary by storefront country. Second, precision: cards abbreviate - Spotify shows "36.2M" reviews and a "1B+" download bracket - while exact figures exist behind the labels; decide which precision your model needs and we deliver the matching columns. Third, history: the store keeps no per-app archive, so any trendline is built from repeated captures - which is exactly what the daily, weekly or hourly cadence is for.