Use the Android Market LVL: http://developer.android.com/guide/publishing/licensing.html
If you pass out an application with the LVL in it, it won't authorize unless you have the same revision number APK uploaded to the market. KEY: You don't have to publish the APK on the market, it just has to be uploaded for the Market to match a license against. If you don't publish it, all copies on accounts that are not the main developer account or in the space provided for you to add additions, will always authenticate as good. If you want that beta to be turned off, simple delete the APK from the market and it will not longer authorize. WARNING: DO NOT publish the APK on the market or you will not be able to delete it. Also, add "beta" in the package name so you can publish the full version and leave the beta running for however long you need. Example steps: 1. Make com.mysoftware.beta.app 2. Implement LVL into the app 3. Upload APK to the market, but DO NOT publish 4. Hand out beta edition 5. Get feedback 6. When finished, delete APK from market to disable beta editions 6b. Or, leave the beta APK and publish com.mysoftware.app so you can continue to beta along with the full version 7. Enjoy! Key Points: 1. DO NOT publish the APK. (hopefully I've said that enough) 2. DO NOT update the revision number unless all your beta testers are going to be able to upgrade. To get the proper authorization, the revision number in the app and on the APK in the market need to be the same. Luckily, since you followed step one and didn't publish it, you can upload the same version number over and over. 3. DO let your testers know the timeline and when you plan to turn it off. 4. DO publish with "beta" or something else in the package name so you can continue the beta or have some overlap. 5. DO remember that anyone can use the BETA APK till you either change the revision number or delete the APK from the market. 6. MIGHT want to add some other authentication via your own server or via Google App Engine (it's free up to a certain usage point): https://appengine.google.com/start 7. Just here because I like to have seven points =) I use this method and it seems to work well. A bit of trial and error was required, so I hope that Google will document a more official way to use it for beta, but I've listed all the things I've run into. Hopefully others can let you know if there is anything I missed. Steven Studio LFP http://www.studio-lfp.com On Sep 28, 9:53 am, Jean-Michel <[email protected]> wrote: > Hi there, > I am at the point where I question releasing my application out in the > wild, but before that I would like to go through a beta phase with > beta testers recruited thru some forum (not my friends from childhood > I mean). > > I am stunned that it seems Google did not plan for this at all... > > I am keen to have beta testers, but not so much that an unlimited/ > unrestricted app leaks all over the place. > This question has been asked already and I was wondering is there were > any new news on the topic... > > Basically, if I issue them an application with a limited lifespan > siging key, I won't be able to use this key on the market (because of > the 2033 thingy). > If I use adifferent key on the market, my beta testers will have to > uninstall the application before being able to install the final > version and they will lose their data. > > If I issue a debug signed application, it can go everywhere unless I > do something (possibly complicated) in my app to restrict it to the > "beta crowd"... > > I am not even thinking about giving the final app for free because it > seems it is another can of worms. > > Any idea welcome, thanks in advance. > JM -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
