App store reviews filed as GitHub issues

Dev toolWeb1 weekNext.jsClaude APIGitHub APIStripe

The idea

Mobile users file their best bug reports in the worst place: app store reviews. A one-star review saying the app crashes on upload since the last update is a reproducible defect report with version metadata attached, and it sits unread because no developer opens App Store Connect daily. Meanwhile the star rating bleeds, and the existing review tools (AppFollow and friends) stop at sentiment dashboards, which is another inbox nobody checks.

The wedge is refusing to be an inbox. Reviews get classified, clustered and delivered into the place work already happens: GitHub issues, deduplicated so fifty crash complaints become one issue with a rising report count rather than fifty notifications. LLM classification is what makes this buildable now; keyword rules were never good enough to trust with issue creation.

Who pays

The buyer is an indie mobile developer or a small studio, paying 15 to 39 dollars a month per app or small bundle, self-serve with a trial. The pitch is concrete: one caught crash cluster protects the rating that drives all their organic installs. Distribution through indie iOS and Android communities, r/iOSProgramming, and integration listings in the GitHub Marketplace.

MVP scope

  • Review ingestion from the App Store RSS feed and the Play Developer API, synced nightly
  • Claude classification into bug, feature request and noise
  • Embedding-based clustering with pgvector so duplicate complaints merge
  • Deduped GitHub issues with excerpts, versions and report counts, appended as clusters grow
  • Regression detection when a resolved cluster resurges after its issue closes
  • Skip for v1: sentiment dashboards, review reply drafting, Linear and Jira targets, Slack notifications
// Build prompt — paste into Cursor / Claude Code / Lovable / Bolt
Build ReviewTriage, a web app that turns app store reviews into deduplicated GitHub issues. Stack: Next.js (App Router) on Vercel with cron jobs, Claude API for classification and clustering, GitHub API via OAuth for issue creation, Stripe for billing, Postgres for state.

Core flow: user signs in with GitHub, adds an app by App Store ID (fetched via the public iTunes RSS reviews feed) or Play Store package name (via the Google Play Developer API with an uploaded service-account JSON), and picks a target repo and an issue label. A nightly cron pulls new reviews since the last sync, storing rating, text, app version and country.

Triage pipeline: Claude classifies each review as bug, feature request, or noise, then embeds and clusters bug and feature reviews against existing open clusters (cosine similarity threshold around 0.8; store embeddings in Postgres with pgvector). New cluster: open a GitHub issue titled with a Claude-written one-line summary, body containing representative review excerpts, affected versions, star ratings and per-store counts. Existing cluster: append a comment to its issue with the new excerpts and bump a report-count line in the issue body. When an issue is closed on GitHub, mark the cluster resolved; if the same cluster resurges afterwards, open a fresh issue that links the old one, flagged as a regression.

Pages: landing, app dashboard with sync status and cluster list, cluster detail, settings.

Pricing: 15 dollars a month per app, 39 for up to five apps, 14-day trial, Stripe checkout.

// More Dev tool ideas