Publish your radio app on Google Play: the run sheet from account to review

To publish a radio app on Google Play you need a verified Play Console developer account, a signed app bundle, a complete store listing, the App content declarations (content rating, target audience, Data safety, privacy policy) and, on a personal account opened after 13 November 2023, a closed test of at least 12 testers for 14 days in a row before Google lets you apply for production. Plan the account and the testers first; they set the timeline, not the build.

Steps
7
Reviewed
Runs on
Shipping the Android build to Google Play
Written by
Get Stream Hosting

By the Get Stream Hosting team

Every step was checked against the software's official documentation by independent reviewers before publishing. Last reviewed .

Pre-flight check

What Google checks before a first release

Google wants to know who you are, what the app is, who it is for and what it does with data. Each item below has its own page in Play Console, and the Dashboard lists whichever ones are still open.

ItemWhere it livesWhat settles it
Developer identityAccount settingsLegal name and address from the linked payments profile, plus one-time codes to your contact email, contact phone and developer email
Device check (personal accounts)Home, task to verify an Android deviceThe Play Console mobile app on a non-rooted Android phone running Android 10 or later
Store listingStore presence, Main store listingName, short and full description, icon, feature graphic, screenshots
App contentPolicy, App contentPrivacy policy, ads, app access, content rating, target audience, Data safety
Closed test (new personal accounts)Testing, Closed testing12 or more testers opted in for the preceding 14 days, then Apply for production
ReleaseProduction trackAn app bundle that passes review

Pick the account type before anything else

The account type decides how long the whole job takes, so choose it on day one. Sign in with the Google account that should own the station's listing for years, not a presenter's personal address.

  • Personal account. Publishes under an individual's name. You verify contact details, prove you hold a physical Android phone through the Play Console app, and, if the account was created after 13 November 2023, run the closed test before production opens.
  • Organization account. Publishes under the station's legal entity. Google will not create it without a valid D-U-N-S number, which Dun & Bradstreet issues free but which can take up to 30 days. You also give an organization phone, website and a public developer phone. The closed-test rule does not apply.
  • Fee. A one-time registration fee is paid with a payment method at sign-up; the current amount is on our Google Play runbook and in Play Console.

A church, school or community station that is a registered entity can open an organization account and skip the closed test; if it has no D-U-N-S number yet, request one now, since Dun & Bradstreet can take up to 30 days.

Store listing: limits to work inside

Write the listing to the limits Google enforces and the upload goes through first time. Use the station name listeners actually type into the search box.

FieldLimit from GoogleFor a station
App name30 charactersThe on-air name, no slogans
Short description80 charactersFormat, city or language, one line
Full description4,000 charactersShows, schedule, how to listen, contact
App icon512 x 512 px, 32-bit PNG with alpha, up to 1,024 KBThe station logo, readable at small size
Feature graphic1024 x 500 px, JPEG or 24-bit PNG, no alphaLogo on a plain background
Phone screenshots2 to 8; each side 320 to 3,840 pxPlayer, schedule, a podcast episode

Set the category to Music & Audio in Store settings and add a support email that someone reads. For the station app on our radio streaming plans (the Premium plan lists it), the panel supplies the icon and feature graphic; you take the screenshots yourself from the test .apk installed on a phone.

App content, answered for a radio app

These answers become public labels and policy commitments, so answer them as the person responsible for the station, not as a formality.

  • Privacy policy. Required for every app, including one that collects nothing. The station app's policy URL is generated in the panel.
  • Ads. Say whether the app shows ads. The station app build contains none.
  • App access. If nothing sits behind a login, declare that. A login-gated app must give reviewers working test credentials.
  • Content rating. Fill in the questionnaire with your real programming: talk content, language, music themes. The rating follows from your answers, and an app with no rating can be removed.
  • Target audience. Choose the age groups you actually serve. Any group that includes children under 13 brings the Families policy requirements into scope.
  • Data safety. Collection means data leaving the device, including through libraries. The station app build has no analytics, accounts or advertising identifiers. Your stream server still sees each listener's IP address to deliver audio; Google treats data held only in memory to serve a real-time request as ephemeral, which still goes in the form but need not show on the listing. The declaration is yours, so read Google's definitions before you submit.

The run sheet: closed test to production

  1. Create the app in Play Console: name, default language, type App, Free. Accept the declarations.
  2. Fill the store listing and every App content item until the Dashboard shows them done.
  3. Personal account created after 13 November 2023: open Testing, Closed testing, and add testers by email list or Google Group. Record the exact Google account each tester uses on their phone.
  4. Upload the .aab to the closed track and accept Play App Signing when asked. Send testers the opt-in link; a tester counts once they have opted in, and each should also install the app from Play and use it, since Google looks at tester engagement.
  5. Keep at least 12 testers opted in without a break. Someone who leaves and rejoins restarts their own count, so recruit spares: presenters, volunteers, regular listeners.
  6. After 14 consecutive days, choose Apply for production on the Dashboard and complete its three parts: the closed test, the app, and production readiness. Google states it usually decides in seven days or less.
  7. Once production is open, create a release on the Production track, add release notes, then send changes for review from Publishing overview if they wait there.

How to confirm it worked: Publishing overview shows no changes waiting, the app status leaves review, and searching the station name in the Play Store app on a phone that is not a tester returns your listing.

Google says some reviews take up to seven days or longer in exceptional cases. Do not announce a launch date on air until the listing is live.

Signing keys, cars and later updates

With Play App Signing, Google keeps the key that signs what reaches listeners' phones, and you keep an upload key that proves the bundle came from you. A lost upload key can be reset through a request in Play Console; it is still slower than restoring a backup. Download the upload key from the panel and store it with its password somewhere other than the computer you build on.

Android Auto is not switched on by publishing. Open Advanced settings, the Form factors tab, choose Add form factor, then Android Auto, and have an Android Auto capable build on a testing track. Car builds are reviewed against Google's car app quality guidelines; a failure on a closed track only warns you, but on open testing or production it blocks the release.

Google also sets a minimum target API level: from 31 August 2026, new apps and updates must target Android 16 (API level 36). If the console refuses a bundle on those grounds, rebuild in the panel and contact support before you upload again. Changes to streams, schedule and podcasts reach the app from the station's feed, so they need no new release.

When the console pushes back

  • Apply for production not open yet. Count the testers who have each been opted in without a break for the past 14 days; a tester whose opt-in lapsed starts their own 14 days again, so you need 12 with unbroken days.
  • Application refused for low engagement. Keep the closed test running, ask testers to actually listen, then apply again.
  • Organization sign-up stalls. Google takes the organization name and address from the linked payments profile; check they match the D-U-N-S record.
  • Rejection email after review. It names the policy area and what to address. Fix that item, then submit again.
  • Approved but not live. Managed publishing may be on; publish the approved changes from Publishing overview.

The iPhone version runs on a different process with its own checks; see the App Store runbook, and the full set of store guides on station app publishing.

Questions people ask

Do I need my own developer account, or can the app go out under yours?

It goes out under your own Play Console account, so the listing, the reviews and the listener relationship belong to the station. Register with a Google account the station will keep. Our runbook walks through each console screen from that point.

Why can't my new account release to production straight away?

Google gates every personal account opened after 13 November 2023: twelve or more testers must stay opted in to a closed track for 14 days in a row. Only then can you complete Apply for production. Organization accounts skip this step, but cannot be opened without the D-U-N-S identifier.

Does a radio app that collects nothing still fill in Data safety?

Yes. Google requires the form from every app on a closed, open or production track, even when the answer is that no user data is collected or shared. A privacy policy link is required too. An app that sits only on internal testing is one of the few exemptions.

How long does Google take to review a new radio app?

Google states that the production access application is usually reviewed in seven days or less, and that some app reviews take up to seven days or longer in exceptional cases. Android Auto builds get an extra quality review that can add time. Leave margin before any announced launch.

Can listeners use the app in the car?

The station app exposes its library through Media3, which is what Android Auto browses. You still opt in under Form factors in Play Console and pass Google's car quality review before it appears in cars.

Which plan includes the station app?

The Premium radio plan lists your own station app alongside podcasts. The free plan covers the stream, the HTTPS listen link and the embeddable web player. The full feature table by plan is on the radio page.

Shipping the Android build to Google Play

Ship the station app to Android

Follow the Play Console runbook screen by screen, from account registration to the production release and Android Auto.