App Revenue Analyzer — iOS and Android App Research

Compare public app metrics and inspect a bounded recent-review sample for complaints and feature requests. App Store IDs/links and Google Play package IDs/links work in one run. For developers, ASO researchers and product teams. No store login or external API key; an Apify account is required.

This is a candidate awaiting owner review. Production remains the previous iOS version until approved.

First useful run

{"targets":["com.whatsapp","310633997"],"country":"us","language":"en","reviewSampleSize":100,"maxApps":2}

Each unique app becomes one Dataset report. The free comparison lives in the run key-value store under COMPARISON, outside the app-report Dataset. SUMMARY records deliveries and partial errors; ERRORS contains failed inputs. Failed lookups are not billed as results.

What you get

Fields	Meaning
platform, appId, name, developer, url	Store identity and listing
rating, ratingCount, price, currency	Store-specific ratings and regional price
version, lastUpdateDate, daysSinceUpdate	Available update information
storeInstalls.minimum	Android lifetime install threshold, not exact downloads
estimates	iOS heuristic lifetime download/revenue bands and assumptions
reviewInsights.sampleSize, negativeReviews	Unique sampled reviews and 1–2 star count
reviewInsights.complaintThemes	English keyword themes among 1–2 star reviews
reviewInsights.featureRequestReviews, featureRequestExamples	Request keyword matches and up to three short source excerpts

Android revenue and modeled download fields remain null. Public install thresholds do not establish actual revenue. iOS downloads use assumed ratings-to-download ratios of 0.5–2%; free-app revenue assumes $0.20 lifetime value per install. These assumptions are uncalibrated, all model confidence is low, and chart positions do not change the model. Paid non-USD prices are not converted or mislabeled as USD revenue. There is no monthly revenue forecast or verified financial data.

Review complaints and feature requests

{"targets":["com.spotify.music","com.whatsapp"],"reviewSampleSize":250,"language":"en","maxApps":2}

Themes cover stability, performance, advertising, payments, login/access and privacy. Keyword matches can contain negation or ambiguous wording; they are leads for manual review, not verified defects. Requests use phrases such as “please add” and “bring back”. Non-English text may remain unclassified. Themes overlap, and the bounded recent sample is not representative of all users. Optional review failures are explicit (source_error); a useful app report remains billable.

Keyword discovery in both stores

{"mode":"search","searchPlatform":"both","searchTerms":["budget planner"],"maxSearchResults":5,"maxApps":10,"reviewSampleSize":50}

Results are enriched app reports with searchMatches containing keyword and source position. An app found under several keywords is delivered and billed once. Search order is not a category chart or a stable market-wide rank. Android search discovers alternatives; it is not a verified competitor recommendation graph.

Bulk metadata with lower resource use

{"mode":"search","searchPlatform":"android","searchTerms":["fitness","notes"],"maxSearchResults":25,"maxApps":50,"reviewSampleSize":0,"maxConcurrency":5}

Zero review sample disables review requests. Limits: 1000 targets, 20 keywords, 50 search results per keyword/store, and 1000 total enriched apps per run. Default maxApps 100, concurrency 1–25/default 5. These are input bounds, not guarantees of source coverage or proven performance at the maximum.

iOS analysis

{"targets":["284882215","310633997"],"country":"us","reviewSampleSize":0,"maxApps":2}

Available chart positions, recommendation shelf and developer-related apps remain iOS-only and best effort. A related-app shelf may be partial. Empty analyze/search input keeps the legacy free iOS demo lookup; platform usage can still cost money. Explicit invalid inputs fail instead of starting a demo.

Compare, export and automate

Read COMPARISON.apps to compare ratings, price/currency, update recency, Android install thresholds and review findings. There is no cross-store download leaderboard: Android thresholds and iOS modeled bands are incompatible. Store rating populations differ; compare currencies explicitly.

The Dataset contains only useful app reports. Export JSON, CSV or Excel in Apify or read the Dataset API. Nested fields may need flattening. COMPARISON, SUMMARY, ERRORS, OUTPUT are separate key-value records. This changes the previous comparison-row layout; update consumers filtering recordType: comparison. Review excerpts are public source text and can contain personal information; reports do not export reviewer names or images.

Price and resource costs

Existing tariff preserved: $1 per 1000 app reports on paid plans; $2 per 1000 on FREE, plus user-paid platform resources. No separate review fee or startup event. One useful app report = one result event. Failed apps and the comparison are not result events. Optional review failure does not make an otherwise useful report free.

SDK-coupled delivery and billing respect the charge cap. A budget stop can leave a partial Dataset, and in-flight requests/shutdown can add platform cost. There is no continuation checkpoint. Read SUMMARY for coverage; a process success alone does not establish completeness.

Coverage and limitations

• Reviews: at most 500 recent records per app, possibly fewer. No full-history promise, statistical sentiment, general multilingual NLP or verified feature roadmap.
• Country selects the storefront, not reviewer nationality. Android language selects locale; iOS reviews use the country RSS feed.
• Public-source throttling, missing apps and changed HTML can reduce coverage. Partial errors remain explicit.
• Revenue/download estimates are not audited finances and cannot validate a developer's financial claims.
• No performance promise for an untested 1000-app run. Candidate measurements and exact build evidence are kept in the release review.

n8n and developer integrations

Use this Actor in your automation or application with the existing community integrations below. An Apify account and API token are required; Actor and platform charges follow the current pricing.

• n8n community node: n8n-nodes-apivault-app-revenue-analyzer. Install package name n8n-nodes-apivault-app-revenue-analyzer in a self-hosted n8n instance that permits community packages.
• Python client and examples: GitHub.
• n8n source and usage: GitHub.
• n8n source and usage: GitHub.

These are community packages. Publication on npm does not establish n8n verification or availability in n8n Cloud. Review the linked package README for supported inputs and setup.