Structured Google Play app reviews with star ratings, review text, app versions, thumbs-up counts, developer replies, and review timestamps.
Mobile app teams, market researchers, and AI developers
The exact schema depends on the collection. These are the commonly available fields to validate in your sample.
review_idapp_idapp_nameratingreview_textreview_dateapp_versionthumbs_up_countdeveloper_replyreply_datelanguagecountryThis anonymized, illustrative record shows the expected shape. Confirm actual fields and values using the sample for your selected collection.
{
"review_id": "GP_84A21",
"app_id": "com.example.app",
"app_name": "Example App",
"rating": 4,
"review_text": "Useful app and the latest update is faster.",
"review_date": "2026-08-12",
"app_version": "8.4.1",
"thumbs_up_count": 17,
"developer_reply": "Thanks for your feedback.",
"language": "en"
}Classify review sentiment and compare rating-to-text agreement.
Identify recurring product, service, feature, or support themes.
Compare ratings, review volume, response patterns, and customer concerns.
Develop retrieval, summarization, classification, and language-analysis workflows.
Measure how feedback changes by version, business, market, or time period.
Before purchasing or training a model, verify the collection date, geographic and language coverage, rating distribution, duplicate rate, missing fields, deleted-content policy, and source-specific limitations.
A current snapshot is suitable for present-state analysis. Measuring changes over time requires dated recurring snapshots collected with a consistent method.
Scope the collection by app, business, country, language, rating, or date range when those filters are exposed by Google Play. We can also discuss recurring delivery and a normalized schema.
Discuss your review data requirementsCompare mobile app, business, product, and hotel review collections from the main reviews hub.