Notes from Robin Puthli\u2019s talk about Device Fragmentation\u00a0among Android devices on the 1st day of DroidCon UK 2012.<\/p>\n
Device fragmentation starts to become a big part of Android development as there are more and more Android devices available. As a result there are a lot of\u00a0different resolutions and screen sizes that need to be taken into account. OpenSignal.com<\/a> has a very interesting report<\/a>\u00a0on their blog that illustrates this fragmentation.<\/p>\n Luckily (device) fragmentation is a very old problem. It had to be solved on operation systems (Window, Mac, Linux, etc), browsers (Chrome, FireFox, Internet Explorer, etc), Java (ME, SE, FX, etc) and more before.<\/p>\n There are roughly nine strategies you can pick from to deal with device fragmentation. \u201cThere is no silver bullet. You have to pick and mix [from the available solutions].\u201d<\/p><\/blockquote>\n The full presentation can be found at Itude Mobile’s blog<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Notes from Robin Puthli\u2019s talk about Device Fragmentation\u00a0among Android devices on the 1st day of DroidCon UK 2012. Device fragmentation starts to become a big part of Android development as there are more and more Android devices available. As a … Continue reading
\nMulti-manual<\/strong>: Phone vs tablet, writing separate code for each.
\nDerive multi<\/strong>: QT<\/a> or J2ME Polish<\/a>, Mono Touch<\/a>, writing pseudo code and then letting the framework generate the rest.
\nOne (size) fits all:<\/strong> HTML5, PhoneGap<\/a>. This approach is based on coding for the lowest common denominator.
\nSingle adapt<\/strong>: Writing adaptive layouts, using 9-patches, fragments.<\/p>\n