You can use the latest. But you can switch which API you are targeting at any moment in Eclipse.
When you target the older API, the IDE will show errors in the places were you used libraries that were not available for that API. If you launch a Honeycomb app with pictures on a preference screen ( android.preference.PreferenceScreen ) GUI on Froyo, the app will just crash with MethodNotFoundException. So if you want to check for compatibility, it is good to switch API's and rebuild. You can use Reflection API to allow a single code base to work on multiple API's One example is the use of startForGround() for a service: http://developer.android.com/reference/android/app/Service.html#startForeground(int, android.app.Notification (scroll down to public final void startForeground (int id, Notification notification)) Also, note that the Android SDK shows on the top right-hand corner which API started to support the given class/method. For deployment purposes, you can also consult this page http://developer.android.com/resources/dashboard/platform-versions.html to see which API is being used most by users. On Mar 14, 8:07 pm, redhoodtech <redhoodt...@gmail.com> wrote: > I am currently starting to develop android applications with Eclipse > and the Android SDK. What is the best API to start with, and do I > have to create an individual app for each API? I've noticed that the > Relative Layout function works better in API 15 rather than API 8. > When I try using the relative layout function in API 8 it doesn't seem > to function properly. > > Thanks, > John R. -- 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
