If you just upload an app to your play developer account, then submitted it for BETA testing:
1 - Is the app actually published
2 - Is the app released on Play store
3 - Do the policies relating to Play Store published (released) apps still apply to BETA versions, bearing in mind its private usage only and the app is still in developement and not beed finalized.
1) Yes
2) Yes but it's only visible for people you've added to your beta group
3) Yes I believe so.
Otherwise you can upload it in alpha. Just few users (testers) could download it.
Related
I believe this question would be a repeat of this question:
Android in-app products not appearing in Play Store or app
but that question does not answer my question clear enough, so I'm asking again.
I have an app that I would like to test the in app payment feature, and I have read that in app products will only be available once the app has been published to at least beta or alpha.
I want to publish the app to beta or alpha, but it seems like in order to get a opt-in URL, you need at least one version of the app released to the public(playstore), if I am not wrong, and I do not want to do this as the app is still in development.
Is there a way to do a alpha testing before releasing no versions of the app to the playstore?
Here is a screen shot of my google play console:
Edited:
Why am I not seeing a opt-in URL here?
So it turns out that it takes like 2, 3 days until the alpha or beta testing goes live. The official documentation does not say anything about it, and it actually makes it sound like it happens instantly.
You'll receive an update to the for your app if you already have it installed on your device.
If you don't have your app installed, download it on Google Play.
Note: It can take a while for you to receive the update.
You can leave the testing program at any time. You can switch to the public version of the app if that's available.
To switch to the public version:
Uninstall the testing version.
Install the public version on Google Play.
Note: It can take up to a few hours before you can download the app's public version.
For current version Of Google Play Console:
Release > Testing > Closed Testing > Alpha
1. Click On Testing (Option Under Release)
2. Select Closed Testing.
3. Select Alpha Track.
4. Upload Your app Bundle or Apk.
Follow these steps on your Console:
1) Complete store listing, pricing & distribution, content rating
2) Upload your apk and release to alpha
3) Complete in-app products (Requires billing permission from manifest)
4) By opt-in url you can test the application
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.
I'm developing an app that I've uploaded to the ALPHA TESTING tab of the console.
But from what I am reading I have to publish it live in order to allow users from a private community to download and test the app?
This defeats the purpose of ALPHA testing. I have to publish my app live to test an ALPHA version. This ALPHA version is not ready for production hence why it's in ALPHA
If this is not the case, how can I install the APK that I've uploaded to the console in the ALPHA testing tab and give access to a group of users?
I don't see a link to it?
Have you read this https://support.google.com/googleplay/android-developer/answer/3131213?hl=en?
Only the users from your Google Group will see your app in a Play Market during this testing.
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: