{"id":602,"date":"2009-10-12T01:14:42","date_gmt":"2009-10-12T00:14:42","guid":{"rendered":"http:\/\/vhirsch.com\/blog\/2009\/10\/12\/more-fragmentation-android-motorolas-motoblur\/"},"modified":"2012-04-25T14:14:51","modified_gmt":"2012-04-25T13:14:51","slug":"more-fragmentation-android-motorolas-motoblur","status":"publish","type":"post","link":"https:\/\/vhirsch.com\/blog\/2009\/10\/12\/more-fragmentation-android-motorolas-motoblur\/","title":{"rendered":"More Fragmentation: Android &#038; Motorola&#8217;s Motoblur"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"margin: 5px; float: left\" src=\"https:\/\/vhirsch.com\/blog\/wp-content\/uploads\/2009\/10\/android_vector1.jpg\" alt=\"\" width=\"132\" height=\"97\" \/>A new round of fragmentation looms. It is something I have been fearing for a while now: that OEM (and carriers) would make use of the open source of the likes of Android and LiMo to produce their very own flavour of apps. So after <a href=\"https:\/\/vhirsch.com\/blog\/2009\/09\/25\/vodafone-360-the-good-the-bad-and-the-ugly\/\">Vodafone&#8217;s 360 announcement<\/a> (with customized LiMo storefronts, etc), Motorola <a href=\"http:\/\/www.fiercewireless.com\/press-releases\/motorola-extends-product-experience-through-partner-ecosystem-its-android-powered-mob\">announced<\/a> so-called &#8220;signature apps&#8221; from a number of developers that are all delivered through Motorola&#8217;s new &#8220;Motoblur&#8221; user interface, which<\/p>\n<blockquote><p>is based on the Google-backed Android platform for mobile systems. Motorola [will] offer an additional SDK for its APIs beyond what is available for Android.<\/p><\/blockquote>\n<p>And <a href=\"http:\/\/www.pcworld.com\/article\/171876\/motorola_will_promote_thirdparty_apps_for_cliq.html\">then it said<\/a> that<\/p>\n<blockquote><p>Over a period of time&#8211;we&#8217;re not there yet&#8211;we&#8217;ll allow the APIs to be available so people can develop many more applications than we can think of ourselves, but it&#8217;ll take us a little bit of time to mature ourselves to a place that we could open up APIs.<\/p><\/blockquote>\n<p><img loading=\"lazy\" decoding=\"async\" style=\"margin: 5px; float: right\" src=\"https:\/\/vhirsch.com\/blog\/wp-content\/uploads\/2009\/10\/Motorola-logo.jpg\" alt=\"\" width=\"102\" height=\"102\" \/>Ouch. An additional SDK. Which is not yet there yet. Whilst the <a href=\"http:\/\/www.motorola.com\/Consumers\/US-EN\/Consumer-Product-and-Services\/MOTOBLUR\/Meet-MOTOBLUR\">Motoblur UI looks actually quite nice<\/a>, this sounds suspiciously like another round of walled gardens, onerous internal and external QA, fragmentation and pretty much a fall back into the traps of the J2ME uber-customized world where one needs to support hundreds of devices for a commercial roll-out (with the trouble of course being that, all too often, that work meant that it would no longer be commercially very sensible). Oh dear&#8230;<\/p>\n<p>It makes one want to call out for a quick advancement of HTML5 with Gears and all, so that one won&#8217;t need apps after all. <a href=\"https:\/\/vhirsch.com\/blog\/2009\/07\/21\/so-google-app-store-or-web-or-both\/\">The issue of connectivity and usability, etc<\/a> would of course still be there. Such despair&#8230;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A new round of fragmentation looms. It is something I have been fearing for a while now: that OEM (and carriers) would make use of the open source of the likes of Android and LiMo to produce their very own flavour of apps. So after Vodafone&#8217;s 360 announcement (with customized LiMo storefronts, etc), Motorola announced [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[756,484],"tags":[50,252,849,343,394,820,434,489,842,697],"class_list":["post-602","post","type-post","status-publish","format-standard","hentry","category-756","category-oem","tag-android","tag-google","tag-limo","tag-limo-foundation","tag-mobile-applications","tag-mobile-web","tag-motorola","tag-open-handset-alliance","tag-open-source","tag-vodafone"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/paSwZv-9I","jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/vhirsch.com\/blog\/wp-json\/wp\/v2\/posts\/602","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vhirsch.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vhirsch.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vhirsch.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vhirsch.com\/blog\/wp-json\/wp\/v2\/comments?post=602"}],"version-history":[{"count":3,"href":"https:\/\/vhirsch.com\/blog\/wp-json\/wp\/v2\/posts\/602\/revisions"}],"predecessor-version":[{"id":1439,"href":"https:\/\/vhirsch.com\/blog\/wp-json\/wp\/v2\/posts\/602\/revisions\/1439"}],"wp:attachment":[{"href":"https:\/\/vhirsch.com\/blog\/wp-json\/wp\/v2\/media?parent=602"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vhirsch.com\/blog\/wp-json\/wp\/v2\/categories?post=602"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vhirsch.com\/blog\/wp-json\/wp\/v2\/tags?post=602"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}