Connect Google Play to your Goodspeed app
Every app builds, signs, and ships to Google Play under your own Play developer account. Goodspeed submits on your behalf but never co-mingles credentials across tenants. Goodspeed wires Google Play into every app that needs it at generation time, so you start with a working integration, not a blank config and a documentation tab.
WHAT GETS WIRED IN
Built into every Google Play build
Every app Goodspeed generates with Google Play includes these wired integrations from the first build. No manual setup required.
| Item | Description | Strength |
|---|---|---|
| Your own service account | You create one service account in Google Cloud and paste the JSON key into Connect Accounts. It is stored encrypted and scoped to your app alone. | Auth |
| Publisher permission only | The account can upload a bundle and manage releases. It cannot reach billing, user data, or anything else in your Google Cloud project. | Auth |
| Keystore managed remotely | EAS Build generates and stores the Android signing key per app, so there is no keystore file to keep safe on a laptop. | Auth |
| Package name set once | Derived from gas.config.ts, and permanent from the first submission to the Play Console onward. | Setup |
| Upload and promote | EAS Submit calls the Play Developer API to upload the bundle, create the release and promote it to the internal track. | Delivery |
| Internal testing track | Pre-release distribution uses the same bundle that goes to production, with no rebuild in between. | Delivery |
| Processing waited out | EAS Submit waits for Google to finish processing the bundle before it calls the submission complete. | Delivery |
| Policy rejections surface | A rejection appears in the admin panel and by email. Retry is a manual trigger once you have addressed the issue in the Play Console. | Delivery |
Source: the Goodspeed app foundation · mobile-distribution/android
REAL GENERATED CODE
A snippet from a Google Play integration the pipeline ships
This pattern is lifted from the engineered plumbing that ships inside every Goodspeed app. The studio generates Google Play integration code like this for every app that includes it, not a placeholder you have to fill in yourself.
Service account + build profile
// Setup: Google Cloud Console → IAM → Service Accounts // 1. Create a service account. // 2. Create a JSON key and download the file. // 3. In Play Console → Users and permissions, // invite the service account email and grant // 'Release manager' rights. // 4. Paste the JSON file into Connect Accounts. // // eas.json Android production profile: "production": { "autoIncrement": true, "android": { "buildType": "aab", "credentialsSource": "remote" } } // Note: reviews, crash reports, and purchase events // do NOT flow back through this integration. // Use Play Console, Firebase Crashlytics, or RevenueCat.
Today's log
APPS THAT USE GOOGLE PLAY
Where this integration ships
These app types include Google Play as part of the generated stack. Each link goes to a full spec page with capabilities, scored ideas, and a pipeline walkthrough.
- Build a fitness tracker appBuilding a fitness tracker means wiring together daily logging, progress charts, Apple Health, and push reminders. Goodspeed generates all of that in a single build, not a patchwork of tutorials. The FITNESS TRACKER APP
- Build a social appBuilding a social app from scratch means solving hard infrastructure problems: real-time feeds, fan-out writes, notification delivery, and content moderation hooks. Goodspeed generates a complete sociSOCIAL APP
- Build a marketplace appMarketplace apps require buyer and seller flows, search with filters, secure checkout, and the kind of review system that builds trust over time. Goodspeed generates all four, wired together on SupabaMARKETPLACE APP
START WITH GOOGLE PLAY