There are 4 CPUs, 3 GPUs, 7 screen formats (with variations on those no less) and 4 memory foot prints for Android right now.
The Dalvik Virtual Machine was developed for the sole purpose to get around those issues. The Android SDK was then developed to allow developers to write one code base using one of several offset XML based layout systems with 3 level of included graphics to properly display the programmers intent.
There is only one problem, the phone maker has to implement the final API conversion routines in the firmware. Guess how many of them are broken?
Now that just covers non-gaming apps. OH I almost forgot, SQLite has several variations currently deployed which means if you have to write several piece of try-catch code segments to account for that issue too.
Fragmentation is not only real it is keeping developers, like me, from even bothering to program for Android. The return on investment simply isn't worth the time for some.
Android is a house of cards right now. One that is teetering. It should be interesting to watch how Google fixes the issues with the 3.x code base.
And keep this in mind. Three years ago Black Berry was the #1 phone. One year ago iPhone was the #1 phone. This year, maybe Android is the #1 phone. I wonder, if things change this fast, who will be #1 two years from now? And remember, three years ago everyone and their dog would have bet you it was Black Berry.
The Dalvik Virtual Machine was developed for the sole purpose to get around those issues. The Android SDK was then developed to allow developers to write one code base using one of several offset XML based layout systems with 3 level of included graphics to properly display the programmers intent.
There is only one problem, the phone maker has to implement the final API conversion routines in the firmware. Guess how many of them are broken?
Now that just covers non-gaming apps. OH I almost forgot, SQLite has several variations currently deployed which means if you have to write several piece of try-catch code segments to account for that issue too.
Fragmentation is not only real it is keeping developers, like me, from even bothering to program for Android. The return on investment simply isn't worth the time for some.
Android is a house of cards right now. One that is teetering. It should be interesting to watch how Google fixes the issues with the 3.x code base.
And keep this in mind. Three years ago Black Berry was the #1 phone. One year ago iPhone was the #1 phone. This year, maybe Android is the #1 phone. I wonder, if things change this fast, who will be #1 two years from now? And remember, three years ago everyone and their dog would have bet you it was Black Berry.