3 ms·
I wonder if you say that SDK was a mess (implying it isn't so any longer), what minimum Android version do you target? [edit] this was a sincere question. I ca
by icoder 14y ago
I wonder if you say that SDK was a mess (implying it isn't so any longer), what minimum Android version do you target?
[edit] this was a sincere question. I can elaborate on it a bit more. Based on the previous submission I reasoned OP is behind the blogpost. If not, my question doesn't make sense.
Why this question? Recently I have the experience, for Android, that developing in a 4.1 world while supporting at least 3.2 is a tricky thing (and since there's quite some version fragmentation on Android, this supporting at least 3.2 is still more than reasonable). For instance, you should/want to use Fragments, but 3.2 doesn't know them. Compatibility library helps of course, but there's gaps in it and if these gaps pose a problem, you're bound to write it yourself or revert to using deprecated code (and not leveraging the 4.1 benefits there). So, no disasters there, but still tradeoffs to be made and I simply wondered what tradeoff was made here (or what part I have been overlooking, of course :). [/edit]