Not only "should" you, you will have to. You won't be able to upload an app with a conflicting package name. Adding a ".adc2" sub-package sounds perfectly reasonable to me, though what you name it is up to you.
- Dan On Mon, Aug 24, 2009 at 11:10 AM, Peli <peli0...@googlemail.com> wrote: > > Does this mean we should choose a unique package name for ADC2? Would > this be recommended? (e.g. can we continue to use the package name > after ADC2 is over, or do we have to choose a new package name if we > switch back to Market?) > > E.g. if in the long run, we would like to use "com.myapp", then for > now, we should use "com.myapp.adc2" or similar in order to avoid a > future conflict? > > Peli > > On Aug 24, 7:48 pm, Dan Morrill <morri...@google.com> wrote: > > This site is using the same infrastructure as the Android Market and > shares > > a unified namespace, primarily to avoid "squatting" issues. That is, we > > want to make sure that if a developer submits an app via ADC2 that an > evil > > third party could not come along and put an app with the same package up > on > > the Market, before the legitimate developer could do so. This would be > more > > of an issue for users than the developer, but it's a case we wanted to > > avoid. > > Thus, we are using a unified namespace with the Market. While this does > > mean a package rename in the future (and means a package rename today if > you > > want to submit an app published on Market after 1 August for ADC2), we > > judged the inconvenience to be worth it to prevent that particular issue. > > > > - Dan > > > > On Mon, Aug 24, 2009 at 10:36 AM, Mark Murphy <mmur...@commonsware.com > >wrote: > > > > > > > > > > The submission site for ADC 2 is now live! For full details, see our > > > > blog post: > > > > >http://android-developers.blogspot.com/2009/08/android-developer-chal. > .. > > > > > Great! > > > > > I am concerned about the following quote from that blog post: > > > > > "As a final note, if you've uploaded a version of your app to Android > > > Market, you'll need to use a different Android package name for the > > > version you submit to the Challenge." > > > > > Will the ADC2 app be used, by anyone, outside of the ADC2 judging > process? > > > In other words, will developers have upgrade issues due to having the > same > > > app published under two package names? For example, if ADC2 basically > > > means authors have to commit to supporting the ADC2 package name > > > indefinitely, or run the risk of cutting off a chunk of their user > base, > > > that is not something to be taken lightly. > > > > > Can we get a bit of clarification on this point? > > > > > Thanks! > > > > > -- > > > Mark Murphy (a Commons Guy) > > >http://commonsware.com > > > Android App Developer Books:http://commonsware.com/books.html > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
