On Wed, Dec 1, 2010 at 7:40 PM, Dianne Hackborn <[email protected]> wrote: > There are very few things forcing people to use separate .apks. Yes, prior > to 2.0, if an API was being made available as a shared library, you couldn't > use android:required="false" to allow your app to still be installed even if > it doesn't exist. That was fixed last year, however, and the devices > running pre-2.0 versions of the platform are fairly rapidly going down. So. > Well, problem being solved.
Except that what you describe is undocumented: http://developer.android.com/guide/topics/manifest/uses-library-element.html and, apparently, has been undocumented for over a year. While I have been quietly pointing this undocumented feature out, based on your assertions that we should be using it, please do not expect the bulk of Android developers to be using features they are unaware of, outside of the occasional [android-developers] post. FWIW, this is reported as: http://code.google.com/p/android/issues/detail?id=10354 -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.0.1 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
