App Store Review Feature Roadmap

Prioritize recurring review complaints and feature requests before a product-planning session. Each finding retains evidence, review counts and transparent heuristic priority factors.

Import a ready-to-run workflow

Use the tested starter inputs in n8n JSON or the Make blueprint. Setup instructions explain import, credentials, output fields and recovery. Download both platforms as a ZIP.

Select your own Apify credential after importing and run manually first. The templates set a $1 maximum run budget, check run success and preserve useful output. The $1 setting is a ceiling, not a fixed charge. Source availability and provider execution limits still apply. No recurring schedule or external destination is enabled by these files.

First run

Live sample: $0.25 per completed report. Replace the example Apple app ID with your app’s numeric ID, choose its storefront, and run. Leaving the example selected fetches real public reviews for app ID 310633997. The demo checkbox does not make this live sample free.

{
  "demoMode": false,
  "sourceType": "app-store",
  "appIds": [
    "310633997"
  ],
  "country": "us",
  "maxPages": 1,
  "maxRecords": 40
}

Native collection is limited to public Apple App Store customer-review feeds. Feed coverage varies by app and storefront.

Analyze your own data

Use a numeric Apple App Store app ID and storefront country, or import app reviews. Public Apple review feeds provide a bounded sample; complete historical coverage and Google Play are not supported.

For an existing dataset, select it with the dataset picker in the input form. The API equivalent is below; replace the placeholder before running:

{
  "demoMode": false,
  "sourceType": "dataset",
  "datasetIds": [
    "YOUR_APP_REVIEW_DATASET_ID"
  ],
  "maxRecords": 1000,
  "maxInsights": 20
}

You can instead paste objects into records. Each record should contain text and its original sourceUrl; optional fields include id, platform, brand, location, rating, date, likes and title. Supplied sources override synthetic demo mode. Dataset reads do not rerun the collector. Any separate upstream collection workflow is outside this report price.

What comes back

One report row in the default dataset contains an insights array, analyzed-record count and finding count. The output links also provide REPORT.md and REPORT.json in the key-value store. Use JSON to preserve nested evidence; use the Markdown report for review.

Each roadmap finding includes evidence, request examples and priority factors such as sample reach, low ratings and matched severity phrases. Acceptance checklists are research templates, not validated product requirements.

Record limits and sample comparison

maxRecords caps raw current records examined at 1–1,000 before deduplication and filtering. maxInsights caps findings at 1–30. A small or unmatched batch can return fewer findings, including zero. The fee is per delivered report, not per finding.

Supply previousDatasetId to compare the current batch with earlier raw review records. This describes differences between supplied samples, not a verified chronological trend. Do not pass a dataset containing completed reports.

Pricing

$0.25 per delivered report, covering at most 1,000 current raw records. This includes analysis of inline records, existing datasets or native Apple reviews. The actor uses one report-delivered event and no additional dataset-row event. See the Pricing tab for the current platform price.

Synthetic previews on the imported-data workflows have no report-event fee. The App Store live sample uses actual reviews and the normal $0.25 report price.

Method and recurring use

Analysis uses deterministic English phrase/rating rules and text grouping; no generative AI model is called. Scores and draft actions are research aids. Sarcasm, negation, uncommon phrasing and multilingual text can be misclassified. Inspect supporting evidence before acting. Topics can overlap, so their percentages must not be added together. Samples do not establish market-wide demand, product capabilities or future business results.

Use the Actor API or Apify MCP with the same input schema. Imported datasets are snapshots; provide fresh source data for repeated analysis. This actor does not directly scrape YouTube, Reddit or Google Maps or start third-party collectors. No external model key is required.

Local run

Requires Node.js 22 or newer. Run npm ci, then npm start. The Dockerfile uses apify/actor-node:22.