Connect Google Play Console to the White-Label Mobile App Customizer
Inside Agency App Manager, link your Google Play Developer account, then register a permanent reverse-DNS package name (for example com.youragency.appname). Both steps must finish before Sparkforge can build the Android app.
This article walks the full Google Play onboarding flow inside Sparkforge's Agency App Manager. You will connect your Google Play Developer account, then register your Android package name so Sparkforge can build and submit your branded Android app.
Before you start
- A paid Google Play Developer account with Admin rights.
- Access to the Google account that owns the Play Developer account.
- A package-name plan in reverse DNS format (for example
com.company.product). The name is permanent after publishing — choose carefully. - Use only lowercase letters, numbers, and periods.
- Stay signed in to the correct Google account through the entire flow.
Step 1 — Connect your Google Play Developer account
- In Sparkforge, open Mobile App from the left navigation.
- Open Agency App Manager. You will see two tiles — Apple App Store and Google Playstore — each with a Set Up button. Confirm the Steps rail on the left shows Distribution.
- Click Set Up on the Google Playstore tile to load the Play Store connection form.
- In Play Store account name, type a short label (your agency or brand). Use a unique label if you plan to connect multiple Play accounts.
- Click the built-in link to open Google Play Console in a new tab. Sign in to the Google account that owns the Play Developer program.
- Confirm you can reach the Developer Console home screen. Accept any updated terms or verification prompts. If you see a permission error, ask the Owner or an Admin to grant Admin access under Users and permissions.
- Return to the Sparkforge tab. Confirm the Play Store account name field is filled and click Save or Continue.
- The Google Playstore tile now shows the account as connected. If it still shows Not Connected, refresh and retry.
If you manage multiple Google accounts in the same browser, open an incognito window and sign in only to the Play Developer account to avoid linking the wrong one.
Step 2 — Register your Android package name
- In the same connection workflow, open the App Setup stage.
- Click Register to create your Android package name.
- Enter the identifier in reverse DNS format (for example
com.youragency.clientapp). No spaces, no uppercase. - Confirm to register. Sparkforge validates the value and shows a success state when registration completes.
- Continue to the next stage of distribution setup, or return later to prepare assets.
Common errors
- Package name already taken: add initials or a region code, such as
com.youragency.clientapp.na. - Insufficient permissions: confirm Admin access on the Play Developer account, or have the Owner grant access under Users and permissions.
- Mismatch with build: the package name in your app's build files must match the registered value. Use the same identifier consistently in your Android project and any related services.
Frequently Asked Questions
Do I need Admin access in Play Console?
Yes. Admin or Owner access is required to manage app registration and distribution settings.
Can I change the Android package name later?
No. Once the app is published, the package name is permanent. To use a different name, you must publish a new app.
What is a good naming pattern for agencies with many client apps?
Use a stable reverse-DNS base plus a client suffix, for example com.agencyname.clientbrand. Keep it consistent across builds.
Do I need a separate Play Developer account for every client brand?
No. One Play Developer account can own multiple apps. Use clear connection labels in Sparkforge so each app maps to the right client.
Was this article helpful?
Thanks for the feedback.