4

Can anyone help me understand how I could use Goggle Developer Console Tracks?

I've read this right here but I'm still kind of lost. How do I package my application for each of this tracks?

Should I have a different applicationId for each track?

How does the tester get the updated test APKs (since they aren't available in store)?

How to cascade from internal to alpha to beta?

Thanks in advance.

Archie G. Quiñones
  • 11,638
  • 18
  • 65
  • 107

1 Answers1

2

Some quick answers:

Should I have a different applicationId for each track?

Absolutely not. Otherwise they will be completely different applications.

How does the tester get the updated test APKs (since they aren't available in store)?

Although the app is not publicly available in the Play Store, the APKs are distributed through the Play Store once they use your private Opt-In link and add them via their email address.

How to cascade from internal to alpha to beta?

Not sure about "cascading" but you can "promote" an app upstream from "Internal" -> "Alpha" -> "Beta" -> "Public".

Hope that helps clear things up a little bit.

Joshua Pinter
  • 45,245
  • 23
  • 243
  • 245
  • 1
    I actually forgot I asked this questions by now. I figured all that out after sometime but I marked your answer and upvoted it for others asking the same question in the future :) Thanks! – Archie G. Quiñones Apr 02 '19 at 01:33
  • had a small doubt , so while signing the app bundle do i create a build variant for each beta,alpha and release tracks?. Currently I see only two build variants in android studio debug and release. So can i sign the release build variant and use it for both beta and release tracks in play console or should i create different build variants for each beta, release ,debug ,and alpha? – user rk May 30 '19 at 07:28
  • 2
    @userrk That's up to you but I believe you can use your `release` build for each of the "Internal", "Alpha", "Beta" and "Public" streams. For example, if you don't have an existing app, you'd likely use the `release` build and just promote it all the way through. But, if you have an existing app released in "Public", you might want to keep your "beta" version in a separate build/branch/flavour so that you can make updates to the `release` build while also working on your "beta" version. – Joshua Pinter May 30 '19 at 14:48