Post beta on Android Market

Question

I want to publish a beta version of my application on the Android market and run into the problem that I cannot download the application with the same package name twice - even with a different certificate. But having two package names for release and beta version causes a lot of problems (for example, you have to change links to different R placements each time)

Is there a most effective / good way around a problem?

Answer 1

with IO 2013, there is now one beta test option: https://support.google.com/googleplay/android-developer/answer/3131213?hl=en

Answer 2

Yes call your package

com.you.app.beta 

Correct all errors in this application. Then, when you go live, just copy the refactoring of the project by the name of your package (Eclipse CTRL + ALT + R in the element), update the manifest and republish it. The beta package is no longer supported by you, and you can even click on the “Unpublish” button or post an update that displays the update screen associated with the new package (i.e. New Market URL)

 com.you.app 

What is the problem?

Answer 3

We download but do not publish beta versions of our applications. After being uploaded to the market, it is assumed that any incoming licensing check is performed from a legitimate installation that has been downloaded by the party and will respond “licensed”. Therefore, our beta testers can test the full implementation, including the licensing code. (Responses to test accounts are also performed for downloaded but unpublished applications.)

When testing is complete, we download the release version using the same package (and sign the certificate) and publish.

Answer 4

I came across this block that discusses Android Beta Testing and feels that this is the best way. So just share it with you guys. Hope this will be helpful to everyone. http://zubhium.posterous.com/android-app-beta-testing

Clicking an app using com.packagename.beta is not a good idea. This creates unnecessary confusion, and secondly, you do not want to get an unstable version in the market in order to get bad marks for your brand.

Answer 5

Why can't you use the same package name for the version? It will also allow your beta users to be notified of an “app update” (that is, in the release of the final version).

If you want to use different package names, one way is to create an ant script that you can run that modifies all imported files and manifest.xml to use the new name. Thus, you have your own code that you are developing, then you can just run your ant script whenever you are ready to load onto the market; let's say "ant beta". This would rename all your packages from com.company.app to com.company.app_beta, and you could publish it on the market.

Answer 6

It’s not good practice to download beta to the market. You only need to download ready-made applications to the market, as this is what users expect.

If you want to beta test your application, it's best to use a private distribution channel.

If you use the same certificate, then an application with the same package name will be considered an update to the previous one. Users will be able to easily update.