What is an internal test track on Google Play?

What an internal test track is

Google Play organises releases into tracks. Production is the public track everyone sees on the store. Before it come three testing tracks: internal, closed and open. The internal track is the smallest and fastest. The developer creates an email list of up to 100 testers, uploads a build to the track, and shares an opt in link. Each tester opens the link while signed in with a listed Google account, accepts, and installs the app from Google Play like any other app, with updates arriving the same way. Because the internal track is meant for the developer's own team, builds there are available very quickly, often within minutes, rather than waiting on the longer checks applied to wider releases. It is the Android counterpart of sending a build to internal testers on Apple's TestFlight, and it uses the same signed app bundle that will later go to production.

How testers join a track

Each testing track has its own list of testers and its own release. For the internal track, testers are added by email address, individually or through a Google Group, up to 100. Closed testing works the same way but supports larger lists and several separate closed tracks, for example one for staff and one for a group of loyal customers. Open testing lets anyone join from the app's store listing, optionally with a cap on numbers. Testers must use the Google account that was added, and they may need to wait a short while after opting in before the app appears for them in Google Play. A tester can leave a test at any time from the opt in page. Feedback reaches the developer privately rather than as public reviews. When a build has been tested, the same release can be promoted from one track to the next, up to production, without uploading it again.

When each track is used, and the 12 tester rule

Use the internal track for the team's first look at every build, especially early on when builds change daily. Use a closed track for a wider but invited group, such as twenty regular customers, and an open track when the app is close to ready and the developer wants feedback from strangers. One rule changes the plan for many first time developers: Google requires new personal developer accounts to run a closed test with at least 12 testers who stay opted in for at least 14 days in a row before they can apply for production access. The internal track does not count towards this; it must be a closed test. Organisation accounts are not subject to the same requirement. Owners who publish under a personal account should therefore recruit at least 12 testers, ideally a few more to allow for dropouts, and start the closed test about three weeks before the planned launch.

Common mistakes

Running two weeks of internal testing and expecting it to satisfy the 12 testers for 14 days rule. Recruiting exactly 12 testers, then losing one who opts out on day ten and having to start the count again. Adding testers' work emails when they use a personal Google account on their phone, so the app never appears for them. Sharing the opt in link without explaining that testers must accept and then wait before the app shows in Google Play. Uploading a debug build instead of a signed release bundle. Leaving the store listing, privacy policy link and data safety form until the day of the production request, when they are needed to move forward. Forgetting to update the build in the closed track as fixes land, so testers report bugs that are already gone. And treating testing as a formality rather than the cheapest moment to find problems.

Where it shows up in OneCraft

Phone apps built with OneCraft are Expo apps, and paid plans can run Expo builds from the app builder at 5 credits each: an Android test build that installs straight onto a phone by scanning a QR code, or a store build, which is the bundle that goes to Play Console. OneCraft does not submit apps to the stores or manage testing tracks: the owner creates the app in their own Google Play account, which costs 25 USD once, uploads the store build, sets up the tracks and invites testers there. A new personal Play account must test with 12 people for 14 days before production, so the owner plans that time in. Builds run on OneCraft's Expo organisation unless the owner connects their own Expo token. The free plan cannot run Expo builds, and OneCraft apps cannot scan QR codes or use the camera themselves.

Questions people ask