Kent wrote: > #1: What is a correct method for selecting package names? I have > started using a convention "com.myAppClass.appname". Where > "myAppClass" is a arbitrary name that applies to a group of related > apps and "appname" is the specific application (e.g. > "com.mycategory.appDemo" and "com.mycategory.appFull"). Is this right?
I would recommend it be the reverse of a domain name that you own (e.g., com.commonsware.whatever). That is what the com.* convention refers to: http://en.wikipedia.org/wiki/Java_package#Package_naming_conventions > #2: What do I do about the app already released as a "com.android" > package? My assumption is to recreate it using the above convention. > What will the effect be on users who want to upgrade the application > through the market ... or will the market even accept an upgrade > version using a different package name? AFAIK, the Market will not accept an upgrade version using a different package name. You will need to release it as a new app. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 1.1 Available! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
