Geek Answers Handbook

Disadvantages of using Android compatibility library on cells

I would like to know your opinion about the disadvantages of using ACL on cellular devices.

I think about using the library for my application exclusively - even when it works on Honeycomb, otherwise I would have to create 2 versions, mostly identical classes.

First of all, I am interested in the functionality (errors) of the compatibility library, its performance and memory usage compared to the built-in Honeycomb SDK. Therefore, if you have experience creating separate classes for both ACLs and Honeycomb, let me know if the results will be worth the effort - should I create repeating classes or go only with ACLs.

As always, thanks for your support :)

+5
source share
1 answer

If you plan to have one binary file for both tablets and mobile phones, your fragments must be expanded from the ACL, otherwise you will create two applications. The advantage of ACLs is that you can create your application once (extending its compatibility classes) and then run these fragments at all levels of the API> = 4.

, , - ACL, , "" Honeycomb - [ ] r4. ( , ).

+3

More articles:


All Articles