Oh cool, so it is easy to switch between SDKs in Eclipse? and emulators i guess?
On Nov 2, 9:50 am, JP <[email protected]> wrote: > After the usual hand wringing to work through an SDK update and get > comfortable there, I've re-released my apps bound against the 2.0 SDK, > 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 with 2.0 are 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 any 2.0 specialties that you > may find in the doc pages but overlook as having been introduced with > 2.0. > > On Nov 2, 5:39 am, dataStorm <[email protected]> wrote: > > > Android 2.0 - Great news! > > > Should all the new apps be developed with the 2.0 SDK? 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 and 2.0 phones? > > > Thanks! -- 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
