what is the best coding strategy for supporting pre-3.0 devices with android support library and after-3.0 without it? [closed]

Question

Closed. This question needs details or clarity. It is not currently accepting answers.

---

Want to improve this question? Add details and clarify the problem by editing this post.

Closed 8 years ago.

Improve this question

Some library has 2 implementations: one for native 3.0 API and another for ACL support. For example Mark Murphy's enhancement for the Loader framework. https://github.com/commonsguy/cwac-loaderex

So how to cope with it?

Answer 1

The general pattern is that you use the backport so long as your android:minSdkVersion indicates that you need the backport.

So, if your android:minSdkVersion is set to 10 or lower, you will:

• Need to use the Android Support package's backport of fragments, if you want to use fragments or loaders

• Need to use ActionBarSherlock or the App Compat backport of the action bar, if you want to have an action bar

• Etc.

Once your android:minSdkVersion rises to the level that you no longer need the backport, you can (carefully) switch your imports and such to use the native implementation of the capability, rather than the backport. Or, in the case of libraries like CWAC-LoaderEx, switch your imports to use the classes that work in tandem with the native implementation of the capability.