I am about to start a closed alpha test for my Android game, that uses Google Play Games.
As far as I have understood, I actually need to publish the game (with an alpha APK uploaded) to receive the correct link, and to start the alpha testing?
I am a bit concerned that I cannot change some things (like delete achievements) even after publishing a test version of my game... am I correct? Or does this apply only when I publish a production version of my game?
This is what the Google Play Games publish button says, even though I haven't uploaded a production APK (just the alpha APK):
Please note that certain aspects of the game cannot be changed after publishing (all fields marked with a padlock) and that achievements cannot be deleted after publishing.
It might take a few hours until the functionality is available.
You do not need to publish the game to the public to start testing achievements. Read this link.
You'll upload an APK to the Alpha or Beta test phases on the Google Developers Console like any other. Once you've done that you will have to whitelist any testing accounts (their G+ accounts). That is also done on the Google Developers Console. Read the link above for how to whitelist accounts.
For resetting achievements read this link.
Resetting achievements is also done through the Google Developers Console. The above link explains the process.
These are pretty simple processes and with those two links you should be able to answer both of your questions and hopefully any other ones you have!
Related
this is a more tightly focused version of the same problem which I've asked about here: App on Play Store invisible to Android 11 devices
In that previous question, I only briefly wondered about signing. Here, I'm deliberately focusing on signing.
In March 2021, the Play Store started asking that I comply with the new v2 signing method whereby the developer must sign an APK before uploading it to the store. I successfully moved over to that method, the APKs are accepted by the Play Store. When I do it wrong, the Play Store rejects the APK immediately on the upload completing.
At some point (and it's hard to say if these things are truly related) I got feedback from people running devices on Android 11 saying they can't see my app in the store at all. Devices < Android 11 continue to see updates that I upload for my app.
I've done a ton of troubleshooting of the AndroidManifest.xml file. See the other question that I linked to higher up. I don't think that's the problem.
I am left with wondering about the signing aspect of the situation. All I can tell you about my certificate is that it's self-signed. Is this a problem for either the Play Store or Android 11 devices?
Thanks for any help.
Michael
No, the certificate you use has no incidence on the visibility of your app in the Play Store or Android in general.
When you say people can't find your app, is it that they can't find it by searching some keywords, or they can't access the Play store listing using a deep link?
There is no real guidance on how to make your app findable on the store using search, it will largely depend on the popularity of your app, the quality of your app, and the competition on the search words with other apps.
I have added Google Play Licensing with my app. As I read through the document to test this features, I need to publish the app in play store at least as alpha release. I was wondering for the development phase is there any other way like sandbox kind of thing where we can test the Licensing?
No, you have to publish to at least alpha to test right now. But your alpha track can have no users, and it won't appear in search in the Play store.
I am currently creating an android game using the Play Game Services for leader boards and achievements. I am currently testing the features under my account because I can clear the leader board when needed. However, I wanted to release an alpha test of my app. When I try to publish my game so my testers have access to it, it says I have to publish the Game Services first or they won't work. But, if I publish the game services can I still use testing accounts and change things? Or will it be final?
You don't need to "release" [edited] your game in order for testers to try out your game. One reason you may get the "I have to publish the Game Services first..." is because you most likely did not complete the Game Services and API setup between Google Play Developer Console and the app itself.
See steps:
https://developers.google.com/games/services/console/enabling#a_create_a_linked_application
Or, less likely, it could be that you still need to upload the APK:
Upload an Alpha or Beta APK, wait a few hours for it to become active in the system, and then add your tester group. This is a good place to start as of the date of my post:
https://support.google.com/googleplay/android-developer/answer/3131213
Some details from the link above:
Set up alpha/beta tests
Using the Google Play Developer Console, you can choose groups of users to beta test different versions of your app.
Testing basics
With the alpha/beta testing tools available in your Developer account, you can test different versions of your app.
You don't need a production APK to publish an alpha/beta app.
Users need a Google Account (#gmail.com) or a Google Apps account to join a test.
If you're testing an existing app that you've published before, only users in your test group will receive an update for your alpha/beta version. If you're testing a new app that you haven't published before, only users in your test group can find and download your app.
After publishing an alpha/beta APK for the first time, it may take a few hours for your test link to be available to testers. If you publish additional changes, they may take several hours to be available for testers.
If you make any changes to your app's Pricing & Distribution page, including setting your app price to Paid or Free, it affects your production, alpha, beta, and any future versions of your app.
Tip: When you're starting a new alpha/beta test, it's a good idea to start with a small group of alpha testers, then expand your test to a larger beta test group.
Definitely make sure to see more at the provided link:
https://support.google.com/googleplay/android-developer/answer/3131213
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.
I'm just getting started with writing Android apps.
I have something I want to make available to a few interested testers, but I'm a long way from having an app. ready for the general public.
How do I make it available for testers without putting it on Play?
If you have a developer account, you can upload the app for testing, visible only a limited audience. This can be done without publishing the app on Play Appstore for the general public.
Google recommends this for Beta-testing and staged rollouts.
You can have a look to this website: http://thebetafamily.com/
On this website, both testers and creators car register. Testers will apply for tests (tests can be paid or not) and app creators can register to present their app and explain what specific parts of the website should be tested: http://thebetafamily.com/features.
I got really good feedbacks from testers there, both functional and technical, even though I did not offer any paid tests for now.
There is also TestFlight: https://testflightapp.com/ but the difference is that you have to gather your own testers team (I did not have a real network of testers to provide ...).