App store review import
Paste your store links. Usero pulls the public reviews from both stores into one inbox, sorts them into bugs, requests, and praise, and lets you turn a clustered one-star bug into a pull request you review and merge.
Your worst bug is hiding in plain sight, repeated across twenty reviews under twenty wordings, split across two store consoles that never compare notes. Each review looks minor. The pattern is the problem.
App Store Connect and Google Play Console each rank a complaint only against their own pile, so a crash that is your single biggest issue can read as a minor gripe in each store on its own. Reading reviews one at a time is a mood, not data: you see one angry star, feel bad, scroll on. The signal only appears when you merge both feeds and group by theme rather than by store or by rating, and that is exactly the work the native consoles will never do for you. What you want is the cross-store cluster, ranked by how often it recurs, sitting next to the rest of your feedback.
How it works
Disclosure: I build Usero, so weigh that. You paste your App Store link (or numeric app id, plus storefront) and your Google Play link (or package name). No store account, no API key, no review-response permission, because public reviews are public. Connect returns instantly and the first import runs on a queue while a panel shows the per-store counts climbing. Then the AI reads the reviews and gives you a first-import breakdown: how many bugs, requests, and praise, plus the single most-mentioned theme across both stores. The wedge runs from there: when a one-star bug clusters, you open the cluster and click Create PR, Usero reads your connected GitHub repo and opens a pull request quoting the reviews that asked for it. You review the diff and merge it yourself. Nothing auto-merges.
Apple and Google reviews import side by side and cluster as one feed, so a crash reported across both platforms is counted once and ranked where it belongs, instead of looking minor in each console separately.
Public reviews are public. You paste a store link or a raw app id / package name. No App Store Connect access, no Google Play Console access, no API key, no review-response permission.
The import filters out star-only and very short reviews, then hands you a bug / request / praise breakdown and the most-mentioned theme across both stores, so you see the problem to fix on the first run.
A clustered one-star bug can become a GitHub pull request from the cluster, with the PR body quoting the reviews behind it. Review to shipped code, not review to a tag in a dashboard.
The honest objection
If you want sentiment charts and to reply to reviews inside the stores, keep that tool, Usero does not replace it and is the wrong fit for that job. Usero is for teams whose product is code in a GitHub repo and who ship it themselves: it ties the clustered review bug to the next step, opening a draft PR you review and merge. A review dashboard shows you the bug and stops. The PR step earns its keep on small, scoped fixes; a vague "feels slow" review clusters fine but is not a one-PR fix. Treat every PR as a strong first draft, not a change to rubber-stamp.
FAQ
No. Public store reviews are public, so importing them needs no store account, no API key, and no review-response permission. You paste your App Store link (or numeric app id) and your Google Play link (or package name), and the import runs from there.
Yes. Fill the App Store field, the Google Play field, or both. The connect button enables as soon as one store parses correctly.
Usero pulls a recent newest-first window of public reviews and skips star-only and very short reviews. After the first import it rechecks both stores every few hours so new reviews land automatically, and Sync now pulls immediately. Re-syncs dedupe by each review stable per-store id.
Connect returns instantly and the first import runs in the background on a queue. A panel polls for status, showing per-store counts climb, then an analyzing phase, then a first-import insight: review counts, a bug / request / praise breakdown, and the most-mentioned theme.
Imported reviews are normal feedback, so a clustered review bug can become a GitHub pull request the same way any feedback item can. You connect a repo via the Usero GitHub App, open the cluster, click Create PR, then review the diff and merge it yourself. Nothing auto-merges.
Free tier. No credit card. Two-minute install. The AI opens the PR, you merge it.