Pick a pre-release distribution method for Android

[markholland]

Pick a pre-release distribution method for Android

[robbiemccorkell]

For iOS, I've been adding everyone from the team to testflight, but I noticed that only "iTunes Connect" users can get updates for every pushed build and there's a small limit to how many users you can have (and arguably the roles give too much access for everyone).

Creating beta tester groups is fine for numbers, but you can only manually give them access to certain builds rather than every build we push, and sometimes it requires app store review.

One of the above tools might be better, and a bit more lenient, for us to use on iOS too.

[markholland]

Agreed, I'll work on getting master deploying both platforms to HockeyApp.

I'm picking HockeyApp as they've been around for a long time and I actively use them.

I'll be leaving TestFlight as is for stakeholder sign off as that is the shortest path of getting a signed off build to the App Store.

[markholland]

Current blocker is where to store the Android keystore for release signing.

We could host the keystore somewhere and have CircleCI curl it which seems to be what most people go for when faced with an open code base.

I'm going to investigate this further using a self generated keystore that is ok to be compromised.

[markholland]

Closing this as we have HockeyApp for Android and iOS is in progress