On Fri, Sep 24, 2010 at 12:23 PM, Mark Wyszomierski <mar...@gmail.com>wrote:
> They'll both have the same package names. > As Pent said, you can't do this, you'll need unique package names. > Should I just change the 'versionName' in the manifest: then upload > Foo.apk as usual (os targets updated of course), and Foo-1.5-final.apk > should be uploaded as a completely separate application to marketplace, > right? > Right. > Then I basically have to tell 1.5 users that they should search for > Foo-1.5-final if they want to use my app, they won't see Foo.apk at all. > > Is that right? > Right. Also, I would upload 1.5-final first, then update Foo WITHOUT any changes so 1.5 users can still see it, but with a message that 1.5 users should get the new version (and point them to it in the market). Then, after like a week to give people a chance to update, do your final 1.6+ Only build and release. More work, but should give you a smoother transition for 1.5 users. Otherwise I don't know how you'd let the 1.5 users know to get the new one considering they won't be able to see the updated one anymore ... ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
