I'm currently working on an application for quite a few months now that should target the largest audience possible, all the way down to 2.2. But I'm getting increasingly confused about how exactly I should deal with the newer Android versions.
I want to be able to use the new features introduced in the newer releases. I also don't want to split the project so that there's a separate version for every major Android release - I know I can put up a different .apk on the Market for different Android releases, but I think this approach would be a disaster to maintain on the long run. I'm currently using fragments heavily, so I have to use the Compatibility Library. I also want to use ActionBars, so I'm using ActionbarSherlock. And my code is currently full of conditional statements that check the current Droid version so I only use newer features (like drag-drop, etc.) if I'm able to. I also have to deal with devices with small screens and large screens, so the navigation is different on them. For this, I also have to support the new resource-identifiers that check the screen's width. It's working alright but things are just getting messier and more complicated with every new Droid release. So is there a silver bullet to this, or are we stuck in the increasingly over-complicated world of backport libraries and conditional class loading based on the current os version? -- 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
