My assumption is we should publish our first build to the Internal testing track, but if Revelry's mobile team has other best practices and/or tooling set up to publish to other tracks, we should consider those for speed's sake.
Scenario: Android Build is Published
[ ] There's a Nightingale Android app in a private track in the Play Store
[ ] Internal users can download, install, and run the app successfully
[ ] The working code and configuration are published in the /nightingale-mobile repo (minus any secrets)
The Play Store currently has 3 testing tracks for Android App releases (see this developer support article):
My assumption is we should publish our first build to the Internal testing track, but if Revelry's mobile team has other best practices and/or tooling set up to publish to other tracks, we should consider those for speed's sake.
Scenario: Android Build is Published
/nightingale-mobilerepo (minus any secrets)