Remote Alpha testing of app with Settings page

Another "how can I" question.
How can I release an app with a Settings page to my alpha testers who are physically remote from my location?
When I install the .prg file created with "Build for Device Wizard" on my watch, the app installs but without a Settings page.
When I install my app published as "DO NOT APPROVE" from the app store, it installs with the Settings page, and subsequent updates from the "Build for Device Wizard" retains the Settings page, but that's not accessible to my Alpha testers.

The "App export wizard" generates a .iq file, but I can't find any description of that. Is there an answer there?

Alan.raceQs over 8 years ago

The simple answer is "you can't", and that's been asked in the Garmin Connect Mobile forums many times...

It might have been nice to point this newbie in that direction at the outset. I've just spent 10 minutes searching the Forum but didn't get any relevant hits to "SETTINGS" in the first 5 pages of results.
Pebble had a private publish option which enabled testers with the private URL to access and download the app from the app store. This worked really well for alpha and beta testers. Alpha testers were sent the link. Later, when we went to beta testing, the beta testers found it under an invitation to join the program on our Web site.

ftrimboli over 8 years ago

Yes. The publish privately feature worked exceptionally well.

The app was not listed in the AppStore, and could only be downloaded by people you had shared the link with. This way, you could test a variety of devices out in the wild (with a small subset of users) without having to release it for everyone.

You could even do this with an update to the app, almost like a "production candidate", to ensure your latest release wasn't going to break something for the thousands of people who use your app.

Maybe this would be a relatively simple feature to add ?

jim_m_58 over 8 years ago

Having the ability to allow some users to beta test something without releasing it to the world as been requested a number of times, as well as have a new version of something with a new beta phase, while allowing the production version to be available to everyone at the same time. (I'd say it's been a year or more)

Both app settings and FitContributor apps need to be in the store to fully check them out (the info to display user added fit data also comes from the app store too)

nairolf123 over 8 years ago

If you really know (and trust) your testers, how about creating a shared "tester" developer account and publish your app in that name with the "DO NOT APPROVE" prefix. By sharing the user credentials for the shared tester developer account among your testers, every one of them can download it "officially".

Coleman.Apps over 8 years ago

Hey Everyone,

Jim is correct that this is an issue that we have been debating for a while. I have created a ticket for our team to do an investigation on how to best achieve this. We always appreciate the feedback and suggestions.

Thanks,
Coleman