Advice for beta versions

Former Member over 10 years ago

I am about to finish a new version of my Golf app. I have added a lot of new features, and re-written quite a part of it. Therefore, I assume that there will be several bugs that need to be found and ironed out.

I don't want to upload the new version and replace the reasonably stable version in the IQ store, because it might upset people if they find the app in their device updated to a possibly unstable version.

Is there a proposed way how to deal with it?

What about uploading the new version as a new app, and initially with a BETA warning?

Can the first version later be pulled from the store? Would it be pulled from user devices as well?

I'm not sure how to proceed and would be glad to get some advice from the store keepers.

Former Member over 10 years ago

I think the best way to do this for now is to upload a Beta version with a different app ID. When you are finished with the beta version you can upload an update to your original app. I would recommend pulling the beta version when you are finished, and not the original, since you want your existing users to see the update automatically once it is ready.

Former Member over 10 years ago

Do I need a new UUID in manifest.xml as well (for the beta and later, when the beta goes mainnstream, again?) or is it sufficient to edit the Appname in resources.xml?

travis.vitek over 10 years ago

You should use a unique UUID for the beta app. If you don't, the user won't be able to have both installed.

Former Member over 10 years ago

You should use a unique UUID for the beta app. If you don't, the user won't be able to have both installed.

Thanks, Travis. Understood, so far. This is basically the same as a second variant of a watchface, copied and then uploaded with a different name and UUID.

However, I'm unsure what to do when the beta goes mainstream and replaces the existing first version. Should the beta then get the original version's UUID or keep the one from the beta or what? (I don't want to keep the beta side by side with the released version - it should rather replace it when it's out of beta).

Former Member over 10 years ago

You should remove the beta from the store and upload your new stable version as an update to your original.

Former Member over 10 years ago

You should remove the beta from the store and upload your new stable version as an update to your original.

Yes, Brian, sure. But what UUID to use? The one from the beta (which is different from the first version of the app to have both in the store while it's in beta), or should the beta get the UUID of the to-be-replaced original stable app?

Let's assume the following:

app 1.0 UUID = 1
beta UUID = 2

Later, when the beta is stable:

app 2.0 UUID = ??? 1 or 2 or 3?

Former Member over 10 years ago

app 2.0 UUID = 1

Nikeow over 10 years ago

sooooo.....
What is to be done for all the beta that has been downloaded? Continue to get bad reviews from clueless users?
Does Garmin encourage/look aside for beta being uploaded to the store?

When app is pulled from the store - entire page is gone or ??
Or just upload a new beta - tricking users to upgrade and then put up a note on the screen that says - this version depreciated. Please update to this version

Former Member over 10 years ago

app 2.0 UUID = 1

Thanks, Brian, that is exactly the information I was after.

Now I'm ready to go.

Former Member over 10 years ago

sooooo.....
What is to be done for all the beta that has been downloaded? Continue to get bad reviews from clueless users?
Does Garmin encourage/look aside for beta being uploaded to the store?

When app is pulled from the store - entire page is gone or ??
Or just upload a new beta - tricking users to upgrade and then put up a note on the screen that says - this version depreciated. Please update to this version

Hi Nikeow

as I understand it (and this was my initial idea anyway), you would upload your beta as a second, parallel app to the IQ store, telling users clearly that it is a beta. If that beta has its own UUID, it would NOT replace the stable, original app (they are basically treated like two completely unrelated apps).

Once the beta is reasonably stable, you would update your original app with the now tested code from the beta, but keep the original app's UUID and name. Users will then automatically update to the stable version.

Normal users who didn't bother to test the beta would experience a normal, smooth update.

You can now either pull the beta or upload the next beta with even more features and new bugs.

Beta testers would (likely) have two separate apps on their device: one released and one beta - both updated when time has come. As long as we name the beta app different from the stable release, it should be easy enough to handle for users.