http://www.opengardensblog.futuretext.com/archives/2007/11/android_fragmen.html Wireless mobility - Innovation - Digital convergence - mobile web 2.0 Thu, 19 Jan 2012 13:47:14 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://www.opengardensblog.futuretext.com/archives/2007/11/android_fragmen.html/comment-page-1#comment-1302 raddedas Fri, 14 Dec 2007 15:05:08 +0000 http://dev5.indigocontenthost.co.uk/archives/2007/11/android_fragmen.html#comment-1302 Android fragmentation is not as bad as JVM fragmentation in the same way that mobile AJAX fragmentation is not as bad as JVM fragmentation - when you have (next to) no installed user base, there's nothing to fragment. As soon as you get volume, you get fragmentation. JVM fragmentation is far less of a problem than non-programmers think - sure it's a pain, but not as much of a pain once you have a little experience as the huge proliferation of screen sizes, native font sizes, etc etc. These will be the same for every platform and will cause problems for everyone; OS and firmware bugs will also hit every platform not just JVMs. Android will have worse fragmentation because it is designed to be completely customisable in a myriad of ways by every manufacturer and/or operator - something the MIDP spec does not allow, in general MIDP just have a few high level APIs either present or not. That is a recipe for fragmentation. Android fragmentation is not as bad as JVM fragmentation in the same way that mobile AJAX fragmentation is not as bad as JVM fragmentation – when you have (next to) no installed user base, there’s nothing to fragment. As soon as you get volume, you get fragmentation. JVM fragmentation is far less of a problem than non-programmers think – sure it’s a pain, but not as much of a pain once you have a little experience as the huge proliferation of screen sizes, native font sizes, etc etc. These will be the same for every platform and will cause problems for everyone; OS and firmware bugs will also hit every platform not just JVMs.
Android will have worse fragmentation because it is designed to be completely customisable in a myriad of ways by every manufacturer and/or operator – something the MIDP spec does not allow, in general MIDP just have a few high level APIs either present or not. That is a recipe for fragmentation.

]]>