[email protected] wrote: > Sorry if I'm jumping the gun & this will be covered by the blog post - > but the thing I'm not getting is how we'll support new (i.e. SDK 1.6) > devices and old (1.5 or earlier) devices at the same time on the > market.
Use resource sets, and ship one version of your app that supports multiple screen sizes from a single APK. My interpretation is that the manifest elements that Al Sutton and Ms. Hackborn were describing are used as market and installer filters -- the app will not be installed if you do not meet the manifest criteria. You might use this, for example, as a stopgap to prevent people from trying to use your app on QVGA or WVGA screens before you have had a chance to add support for them. So, if you want one app to handle more than one screen size, write your app to handle more than one screen size, and leave those manifest elements out of it. Again, this is an educated guess, based upon what we had been told for the last ~15 months on this issue, and it could be they have a whole 'nuther system in mind now. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 1.0 Available! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
