They could have a wrapper class that detects and uses the 3.0 API if it's there, and otherwise does some fall back behavior that looks good on older versions.
On Feb 3, 6:20 pm, Streets Of Boston <[email protected]> wrote: > I read this on android-developers.blogspot.com, from > Dianna:http://android-developers.blogspot.com/2011/02/android-30-fragments-a... > > Quote: > "To address this, we plan to have the same fragment APIs (and the new > LoaderManager as well) described here available as a static library > for use with older versions of Android" > > ... where "this" is the issue you're asking about. > > One thing i'm not quite understanding: > "Our goal is to make these APIs nearly identical, so you can start > using them now and, at whatever point in the future you switch to > Android 3.0 as your minimum version, move to the platform’s native > implementation with few changes in your app." > > What happens before our app's minimum version is set to Android 3.0? > We would ship the app with the static library. This would mean that > even Android 3.0 (and higher) devices would run this static library > instead of its 'native' implementation. Or will there be some 'magic' > compatibility code that kicks in making use of the 'native' > imlementation? > > On Jan 28, 6:32 pm, Zsolt Vasvari <[email protected]> wrote: > > > > > > > > > What are the best practices to maintain an app that would run on both > > Honeycomb and pre-Honeycomb? I do want to make use of Fragments and > > the other goodies, but I have a feeling this will be a major > > P.i.t.A. I certainly don't want to maintain 2 separate apps. -- 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
