Originally Posted by jfanning
Except you claim differs from Googles published stats.
Please provide further details to backup this "pathetic" claim
You say no one codes for ICS, then you say an ICS app won't run on GB, which one is it?
And there are ICS only apps
Actually that is wrong, you can produce apps that run on GB and also use JB features. Also on a JB phone you get to use UI improvements that JB brings
If the app is forward compatible as you say, then doesn't that mean 100% of people can buy you app?
Here's the official numbers right from Google. Accurate as of their last update, Oct 1st, 2012. This is where I got my numbers from and you're telling me I'm wrong?
Read these links on Android and ASLR (address space layout randomization). This is something iOS had since before iOS 5.
And this is only one specific area. Would you like me to go over additional ones?
I was being facetious when I said nobody codes for ICS. But I might as well have been telling the truth based on the very small number of Apps available that actually take advantage of ICS or JB. The bottom line is most Apps are coded for Froyo or GB.
Yes you can write Apps that will use JB features if it's running on a JB device and not use them if it's on a GB device, but that's a crappy way to write software. That's like having multiple versions of an App inside one and selecting which portions to run based on what OS the App detects. It's a hack workaround to solve Androids terrible fragmentation problem.
Forward compatible means an App coded to Froyo will run on all versions up to JB. So what? That's nothing to brag about. The issue is that an App using features of JB will not work on older versions (or if the developer has done the "hack" I described above, then the App will run on older versions with reduced functionality).
Either way you're making compromises. As I said, it's a crappy way have to write software.
Edited by EricTheHalfBee - 10/18/12 at 8:15pm