Our upgrade to 2.0 was mostly painless and switching between SDKs and emulators works OK.
We are trying to figure out how best to test against 2.0, other than the emulator, as there is no 2.0 image available for the ADP. On Nov 2, 7:02 pm, dataStorm <armags...@gmail.com> wrote: > Oh cool, so it is easy to switch between SDKs in Eclipse? and > emulators i guess? > > On Nov 2, 9:50 am, JP <joachim.pfeif...@gmail.com> wrote: > > > After the usual hand wringing to work through an SDK update and get > > comfortable there, I've re-released my apps bound against the2.0SDK, > > into a world of 1.5 and 1.6 field devices. After a week, I have heard > > no complaints, so backwards compatibility seems not much of an issue > > as far as I can see. It is important to note that calls to classes > > introduced with2.0are off limits, such as AccountManager. If you > > want to make sure you don't accidentally cross the line while immersed > > in coding, I'd recommend to use Eclipse and switch to 1.6 during > > development. This will conveniently flag any2.0specialties that you > > may find in the doc pages but overlook as having been introduced with > >2.0. > > > On Nov 2, 5:39 am, dataStorm <armags...@gmail.com> wrote: > > > > Android2.0- Great news! > > > > Should all the new apps be developed with the2.0SDK? I've heard that > > > there are problems with some of the Android Market apps running on the > > > review versions of the DROID. > > > > Should I release 2 versions of my app for 1.6 and2.0phones? > > > > Thanks! -- 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
