We recently decided to update our new application for Beta release on google play,
Now after reading the guide, there were some questions that I had in my mind and wanted to know more about them, I googled for further understanding found some answers but there are still somethings that I wasn't sure about so decided to put this question up:
For Beta releases is it possible to make a beta release that is available to all the google play users(as a normal production app) or will it be available to all?
(Since as per this guide it gives me an idea that the application will only be available to a set amount of users.)
Make sure users can join the tests. Your testers will need to have a Google account (#gmail.com) or a G Suite account to join a test.
Run tests internally. Use the internal testing track to push your app to up to 100 internal testers in seconds.
Once I release a beta application and I decide to now put it for production, will it be uploaded as a different application or the same also will the comments that were posted to the beta release google play app be visible on my production app?
(Didn't quite get anything in relation to this one.)
In one of the points, it said that my application should have a higher version code in the beta release then that of the production release, But if I have a higher version in that release would it not be the application that will be getting downloaded even when it might not be the most stable version? (this one actually confused me big time)
Check your Android App Bundle version number. For an app on the internal, closed, or open testing tracks to be available to testers, it must have a higher version code than your production version.
Is there a designated field where I can provide this email for the beta testers or can I just provide it in the description of the application?
Provide a channel for testers to send you feedback. For closed tests, offer testers the ability to provide feedback by email, at a website, in a message forum, or through another suitable mechanism.
For Beta releases is it possible to make a beta release that is available to all the google play users
You can release your app as an Open Beta, which anyone who wants can get access to (without being invited by you). See https://support.google.com/googleplay/android-developer/answer/3131213?hl=en (specifically the part Step 1: Set up test details - Open test: surface your test app on Google Play)
Once I release a beta application and I decide to now put it for production, will it be uploaded as a different application or the same
Same. There's no re-uploading - you just change the state of the release.
also will the comments that were posted to the beta release google play app be visible on my production app?
Testers can't leave public reviews on Google Play.
But if I have a higher version in that release would it not be the application that will be getting downloaded even when it might not be the most stable version?
Well, that's the point.They have opted in to be testers of your app, so they get the latest available version. If they want to revert back to only getting production versions they can opt out of the test program.
Is there a designated field where I can provide this email for the beta testers or can I just provide it in the description of the application?
This is explained on the page I linked to: Next to "Feedback channel," add an email address or URL to collect feedback from testers. Your app's feedback channel will be shown to users on your tester opt-in page.
Beta releases are just a different track on your app's page.
If you have a public beta program (you'll need to select that as your type), users will see a "Join Beta Program" card somewhere on your app's Play Store page when they visit it. This card should show up below the "Developer Contact" information.
If a user decides to join the beta program, they'll get any new versions you publish there just like a normal update. Beta users cannot leave reviews! Beta users can leave you, the developer, private comments, but unless they leave the beta program, they can't create a review or edit an existing one.
Once you promote your beta build to production, it'll be available to all users of your app as a normal update. Beta users won't receive an update, since they're already on the version you promoted, nor will they be pushed out of the beta program. If you upload an APK straight to production, beta users will receive it as well (they still won't be able to leave a review).
As for version numbers, you can't upload another APK to the Play Console unless it has a later version code than the latest one already uploaded. If you have version 7 in your production channel, you can't upload a new APK with version 7 to beta; it has to be version 8.
When you upload your app as a Beta version, The users who joined your beta testing can upgrade to that version. The other users who have not joined beta testing, will no see any update for your app.
When you want to make the beta version as a production release, you can do so by simply clicking on Promote to Production option on Google Play Store.
With concern to your confusion, when you have some apk in beta version (say versionCode 2), then you can promote that app as a production, or you can also upload another apk as a production but remember, that should have greater version code (say 3). If you do so, then all users will get that update including beta testers. That will be an update to the same app.(I think you're doubtful here) Hope this helps.
Related
I need that my beta testers have the beta app to let them test it but at the same time they must to have the production app to work in production.
The problem is that seems if they become a beta tester only can get the beta app from the Google Play.
There is a way to have both version in the same device without to have to change the app name?
Thanks a lot.
At the moment this is not possible by design. Beta testers are ideally users who get a slightly earlier version of your app, and use it day to day so you discover issues. The thinking behind this decision was that if you allowed both, then if issues were discovered beta users wouldn't report them, they would just switch to the prod app. Also, as an app developer the beta version should be "production ready" according to your internal QA.
This has value for other reasons. Beta users can't leave public reviews - instead they send private feedback. If you allowed both, then you wouldn't be able to have this feature.
A few well known apps (like Chrome) want users to be able to have both apps. For these apps, they have a separate package name for the Beta version and maintain a separate store listing: Chrome Beta, Chrome.
If you did this it would allow both to be installed. But you would have to maintain two store listings, two sets of reviews etc.
The short answer is No, it can't be done.
Update: it turns out the suggestion below is not true...
But you could sort of achieve this by defining multiple user accounts on the device. Create a second user account on the device that uses a different, not-in-the-beta Google account. User accounts have their own distinct set of installed apps, so you could then switch between the two user accounts to use the beta or prod app.
After some developments after releasing the app to production a bug was reported that I couldn't replicate in the latest version. So I needed to check the production version. As they both have the same name I knew I couldn't have both, so I tried to replace the beta version by the production one.
This is what I found out about how to do it.
Step 1. In my phone I went to the app page but the store insisted to install the beta version.
Step 2. In my phone change the account to one whithout beta test access. The play store detected the other account and installed the beta version.
Step 3. Finnaly I went to the store in my desktop and logged in whith the normal account I have on my device! This worked! The production version was in my phone and I could test it!
So my solution to you is this:
You can't have the two versions simultaneously in the same phone except if they have different names.
But you can replace the beta by the production one if you have two accounts on the phone and
A) Loggout from the account with access to the beta version and then install the production one,
or
B) Install from a desktop.
I need that my beta testers have the beta app to let them test it but at the same time they must to have the production app to work in production.
The problem is that seems if they become a beta tester only can get the beta app from the Google Play.
There is a way to have both version in the same device without to have to change the app name?
Thanks a lot.
At the moment this is not possible by design. Beta testers are ideally users who get a slightly earlier version of your app, and use it day to day so you discover issues. The thinking behind this decision was that if you allowed both, then if issues were discovered beta users wouldn't report them, they would just switch to the prod app. Also, as an app developer the beta version should be "production ready" according to your internal QA.
This has value for other reasons. Beta users can't leave public reviews - instead they send private feedback. If you allowed both, then you wouldn't be able to have this feature.
A few well known apps (like Chrome) want users to be able to have both apps. For these apps, they have a separate package name for the Beta version and maintain a separate store listing: Chrome Beta, Chrome.
If you did this it would allow both to be installed. But you would have to maintain two store listings, two sets of reviews etc.
The short answer is No, it can't be done.
Update: it turns out the suggestion below is not true...
But you could sort of achieve this by defining multiple user accounts on the device. Create a second user account on the device that uses a different, not-in-the-beta Google account. User accounts have their own distinct set of installed apps, so you could then switch between the two user accounts to use the beta or prod app.
After some developments after releasing the app to production a bug was reported that I couldn't replicate in the latest version. So I needed to check the production version. As they both have the same name I knew I couldn't have both, so I tried to replace the beta version by the production one.
This is what I found out about how to do it.
Step 1. In my phone I went to the app page but the store insisted to install the beta version.
Step 2. In my phone change the account to one whithout beta test access. The play store detected the other account and installed the beta version.
Step 3. Finnaly I went to the store in my desktop and logged in whith the normal account I have on my device! This worked! The production version was in my phone and I could test it!
So my solution to you is this:
You can't have the two versions simultaneously in the same phone except if they have different names.
But you can replace the beta by the production one if you have two accounts on the phone and
A) Loggout from the account with access to the beta version and then install the production one,
or
B) Install from a desktop.
I have an Android app on Google play store with alpha and beta testers (in addition to production) and so far everything was working well.
I am trying to add a new user to the closed beta testing list on google play store. This user is already using the app on production.
For some reason, although his email address is in the beta testing list, he cannot see and download the version that is published to beta. (Only the version on production).
Any reason for that or a way to fix this?
Edit:
I continue to experience this problem: Once a user have already downloaded the app on production, he cannot become a beta tester. Does that make sense?
After chatting with a Google Play representative, I have finally solved the mystery:
First, a user must uninstall the production app and only then he will be able to see and download the alpha/beta version through the Play Store. (He must also follow the invitation link of course).
Second, surprisingly, when you promote a version from alpha to beta - alpha testers can no longer download this version. More precisely, according to the representative -
"When you promote to beta the testers need to opt-out of the alpha test using the same opt-in link, then uninstall the app from their device, and wait 24 hours"
This in some of the cases was my problem since I assumed alpha testers can still have access to the new app version after it is promoted to beta.
There is a way to have both production and beta versions.
You need a fresh beta release, which means its build code should be higher than your production release.
You need to invite/add the beta testers, ask them to follow the link to take part in the testing etc.
The beta testers need to wait few hours for the beta release to roll up. Probably also have to remove the production version.
Background
The Android developer console has 3 tabs for publishing the app's apk file:
alpha, beta and production, as shown here:
as I recall from one of Google IO lectures, one cool way to check how good is your app before making a 100% scale publishing, is to allow only a percentage of the users to download the app first. I think it's called "staged rollouts" , because you can rollout the publishing in case it had too many problems to be published to all.
My question
What is exactly the difference between them, especially between Alpha and Beta?
Only the production stage is available for people on the play store, right?
which one/s allow to publish only to specific people/percentage , and in which way do you do it?
which stage allows in-app billing, at least for testing ? I don't get why can't i test it out even before uploading the app.
in the percentage method, if I publish a new app version using the same way, will it first update for the people who were lucky enough to install the previous version?
To answer your questions:
What is exactly the difference between them, especially between Alpha and Beta?
There isn't much difference between the two aside from the fact that you just start with a small number of testers for alpha testing and switch to a bigger group for beta
Only the production stage is available for people on the play store, right?
By default, only production is available on the Play Store. However, you can now add an option in your Play Store page for users to opt into an open Beta program. Link
which one/s allow to publish only to specific people/percentage , and in which way do you do it?
You can do that for both. To do alpha,beta testing you need to send invites to people on their google+ accounts so that they can access your app and be able to download it. The invites is usually in the form of a link directing them to your app on the play store which is only visible to them after they accept the invite
which stage allows in-app billing, at least for testing ? I don't get why can't i test it out even before uploading the app.
You can do in-app billing for both alpha,beta testing. Check the link:
http://developer.android.com/google/play/billing/billing_testing.html
in the percentage method, if I publish a new app version using the same way, will it first update for the people who were lucky enough to install the previous version?
As far as my experience goes, I have seen people who were testers get the update for the app first than everyone else. But I am not so sure about how does it work exactly.
Difference between Alpha and Beta testing (Software/Apps Testing)
Alpha Testing is conducted within the organization and tested by an individual developer or a team of developers or testers. This testing is closed for public.
Beta testing is conducted by the end users who are not programmers, software engineers or testers. This testing may be open for public.
Open or Closed Testing
Closed Alpha Testing: This testing is conducted within the organization and restricted by email or group invitations only. Those who are added onto the list of alpha testers on Google Play Store have access to test app.
Open Alpha Testing: Those who have Opt-in link of app have access to test the app. This testing is not restricted by email or group invitations. You can limit the number of testers on Google Play Store.
Closed Beta Testing: This testing is conducted outside the organization and restricted by email or group invitations. Those who are added onto the list of beta testers on Google Play Store have access to test app.
Open Beta Testing: This testing is conducted outside the organization and it is not restricted by email or group invitations. This testing is conducted in real time as the app will be made open for public to install. You can limit the number of testers on Google Play Store.
Generally, alpha testing is first conducted by developers or testers within the organization. Beta testing comes after and is conducted by non-technical or end users outside the organisation. Finally, after completing the testing, the app goes to production.
In app purchase
Licensed users may purchase your in-app products without any resulting charges to the user. Test purchases can be only used in both alpha and beta releases.
To add user license: Google play Console -> Settings -> Developer Account -> Account details -> License Testing
Learn more about testing
#user2511882's answer is great, but there are more information to add.
First of all, alpha and beta channels are designed to test multiple version of app. You can test only one version (identified by versionCode) on each channel, so alpha and beta channels provide two test tracks.
However they have a little difference on test type. You can run closed alpha and open beta test simultaneously, but it's not possible to run two open alpha/beta test nor open alpha and closed beta test.
Another difference is that alpha test APK's version code should be higher than beta test one. If you upload higher version of APK on beta test channel, alpha test will automatically be closed. (This principle applies for production APK too. APK version code should be 'Production < Beta < Alpha'.)
For more details, check this help.
See there are Four types of releases on play console for android developers;
1. Internal testing - It means you wanna share your app among the decided members. It means you have to put their Gmail into the testers list. This is usually for employees.
2. Alpha testing - Same as internal testing, but this time you can send your app to your friends, families, or on your smartphones.
3. Beta testing - This is a serious matter, this is public testing. But people cannot give reviews to your app. You can also limit how many users can install the app.
4. Production - This is the last release, now everybody can install your app, can give reviews, can report to google play if something bad is there. One more thing, now your app appears in play store search listing.
Now there is one more thing, open testing, closed testing, pausing tracks and stage rollouts, don't get confused by these terms.
1. Open testing - It means that you don't need to invite them, like no need to take their Gmail and add it to the user list. (Beta testing)
2. Closed testing - It means that you need to specifically add the user's Gmail into the list. (Alpha testing)
3. Staged rollout - This means we can provide the update to some percentage of users we currently have. Suppose 100 users are there and you rollout for 40% then only 40 users can update the app and after you confirm the app is working perfectly (using crash reports or reviews) then make it available for everyone.
4. Pause Track - See each testing has a track in play console. So if you click the pause track in beta testing then it will pause beta testing [changes occurs in few hours]. Same in internal and alpha. We usually pause test tracks when we release the app in production [usually I do].
Your app will not appear in search results until it is in production.
How do I upload the beta version of the app .. In developer console we have 3 categories to upload , one Alpha testing and second is Beta testing and 3rd is production I have to publish beta version of the app. what should I do? Should I go to upload APK in Beta segment and promote that to APK or something else please remember I am asking about the beta release of the APP not beta testing?
Apps that are published as Beta are not listed in the Play-Store!
If you want someone to test it, you need to invite them (via G+) and send them an Opt-In-Link.
If you want to promote your App, just publish it normally and mention that it´s still in Beta.
EDIT: You can still promote an App that is in Beta to "normal" (production I think), no need to reupload or anything.
The previous reply is a little bit outdated (10 years), so here's an updated information:
see here for early access release:
Playstore : How to release early access app?
and here the direct information from the Google:
https://developers.google.com/assistant/console/releases?hl=en
Basically you have these options:
Draft
Alpha - only users who knows about the app, no review required
Beta - early access, requires review
Production - before review
Released/To-be-fixed - after review
Here is the scheme from the Google page: