4 ms·
I don't think the problem with the Android situation is that users don't get the new OS. The bigger problem (for me at least) is the frustration of being locked
by tseabrooks 15y ago
I don't think the problem with the Android situation is that users don't get the new OS. The bigger problem (for me at least) is the frustration of being locked into 2.2 unless I want to greatly reduce my market size when writing android apps. My iPhone apps can target 5.0 and get 95% of the market. If I go to 2.3 I lose ~20+ percent of the market. Let's not even consider what you lose by going to 3.0+.
- clarky07 15y agoand the fact that 3 isn't current, 4 is. if you develop for the latest and greatest you get what, like 5% of the market.
- fpgeek 15y agoIt really depends on what latest-and-greatest features you want for your app. Google (and a few others) have invested a lot of effort in porting back new Android features with compatibility libraries (e.g. Fragments) so what you want is covered by them, there's little or no compromise. On the other side, Google has also developed a careful reflection / late-binding framework that often makes it straightforward for apps to gracefully degrade their uses of new APIs. That gives developers another way to take advantage of new features while retaining broad compatibility.