Point Claude Code at gplay and it drives your entire Google Play release flow — upload, staged rollout, promotion, listings, subscriptions, crash triage — from natural-language prompts. Here's how, with real prompt transcripts.
Google Play API auth breaks in maybe six different ways — missing API enablement, wrong service account role, key rotation, missing scopes, developer invite pending. gplay auth doctor checks all of them in one command, and can auto-fix most.
Google Play ASO — App Store Optimization — used to mean spreadsheets, screenshots of competitors, and a lot of copy-pasting. Combining gplay with an AI agent turns it into a one-hour audit-to-submission loop across all your locales.
Skip the Play Console web UI entirely — upload an AAB, assign it to a track, add release notes, and run a staged rollout with a single CLI command.
Google Play supports over 80 store-listing locales. Setting them up in the web UI is a click-fest; doing it from a terminal is a for-loop. Here's how to discover, validate, and localize listings and release notes with gplay.
You have Fastlane metadata in fastlane/metadata/android and a supply lane that ships builds. Here's how to migrate to gplay without losing your listings, screenshots, or muscle memory — in about an afternoon.
You don't need the Play Console web UI to inspect an app's state — listings, tracks, releases, review status, subscriptions. gplay reads and writes all of it. Here's a cheat sheet of the commands you'll use every day.
RevenueCat handles the entitlement, offering, and paywall abstraction. gplay handles the actual Google Play subscription, base plan, offers, and per-country pricing. Together they cover the whole subscription stack — from the terminal.
A complete GitHub Actions workflow that uploads an AAB, promotes it through internal → alpha → beta → production with fractional rollout, monitors crashes between stages, and rolls back automatically if vitals regress.
Keeping Google Play prices, RevenueCat offerings, and per-country pricing in sync manually is a full-time job. gplay handles the Play-side PPP conversion, RevenueCat MCP handles the offering-level equalization. Here's the whole flow.
The official Google Play purchase verification story assumes a JVM backend and OAuth boilerplate. gplay collapses receipt validation into a single command that works in any language, any runtime, any CI job.
You installed gplay and ran gplay setup --auto. What next? Here are the five commands to run first — to prove the auth works, understand your app's current state, and start automating things.