May
12
2012
0

This is Android’s fragmentation. And it is still a feature [opinion]

This image has no alt text

This particular image by popular app developer Animoca has done the rounds of world wide web this past week, used by several blogs as yet another “proof” of Android’s fragmentation. Even Chris wrote it about it yesterday. The Hong Kong-based developer says they have over 400 test devices to ensure their apps will be compatible with anything their work is put on.

Damning? Hardly. Android is fragmented, it was always intended to be, and therein lies the beauty of the platform. Everything from TVs to watches run on Android currently. What Android does exceptionally well is that it allows manufacturers to produce any device they wish, without any restriction, so as to offer users as many choices as possible. And it also does well to allow developers to target as many varying form factors with the same code.

The focus on that last sentence should be on the word quality. And what I mean by that is a developer who understands the platform, acknowledges the constraints fragmentation puts on it, and strategizes development accordingly. It might be more difficult to develop for Android than other platforms (though, personally, I found it easier because of my previous experience with Java) but with the slightest of research, you know when you first start what you’re getting yourself into. And, anyway, other than apps that have specific hardware-platform requirements, developing for Android is far easier than web-development.

Also, Animoca goes on to mention that one of their biggest problems is the throngs of entry-level phones available in China. This is a problem specific to a few regions (primarily developing countries, such as India too). And it’s a good thing these phones are available, because they have brought down the price of smartphones to such a degree that nearly everyone can now afford to skip feature phones, and get an Android device (even if of highly limited capabilities).

This is a good thing not only for Android, not only for developers, but the entire smartphone industry in the long run. Also, I have to give props to Animoco for having understood the purpose of fragmentation in Android by not cribbing about it, but instead saying:

“We like fragmentation as users prefer choice. We are not big believers that one size fits all.”

As I wrote back in February, there’s not much Google can now do to turn this fragmentation and other side-effects that come along with an open-source system. So everyone, please, skip this pointless hoopla around “fragmentation”.

 

It isn’t a bug, it’s a feature.

 

 

 

 


Written by admin in: android |
May
11
2012
0

MirrorLink Finds New Supporters, Now 50 Members in Consortium

MirrorLink Finds New Supporters, Now 50 Members in Consortium
The Car Connectivity Consortium (CCC), the organization driving the MirrorLink standard that connects smartphone with dashboards, announced this week at the CTIA trade show in New Orleans it has surpassed the 50 member mark.

These members are currently representing 70 percent of automotive and 70 percent of smartphone markets worldwide with th…

Written by admin in: News |
May
08
2012
0

Weekly OSM Summary #42

April 23th, 2012 - May 7th, 2012

A summary of all the things happening in the OpenStreetMap (OSM) world.

  • The latest news about the license change and the data rebuild-process.
  • The OSM project has more than 600 000 registered members now. Pascal created a new webpage which shows the latest active members. You will find the blog post here.
  • Apple’s new iPhoto attributes the OSM project as a source now.
  • The State of the Map US will take place in Portland on October 13th and 14th, 2012.
  • Six OSM projects have been accepted for this year’s Google Summer of Code.
  • The next Wherecamp Berlin will take place on June 22nd and 23rd. You can already register here.
  • What we can learn from Wikipedia“ a new blog post by Frederik Ramm.
  • Dan Stowell wrote a blog post about how he made a nice map handout from OSM.
  • An online cycle map of Oxford was developed based on OSM data and created with Maperitive.
  • The “Worst Of OSM” webpage shows some failed OSM mapping or import efforts.
  • The new HOT Technical Working Group will start their first IRC Chat on Thursday May 10th at 3pm GMT. Read more here.
  • The “Waymarked Trails: Hiking” webpage is available in seven new languages now.
  • The new Maperitive version can create its own Walking papers now. You will find a description here.
  • A new version of the Overpass API is available. You can find all changes and new features here. For all new readers: The Overpass API is a read-only API that serves up raw XML encoded OSM map data.
  • A new plugin for the Leaflet open source library enables a feature to display GPX or KML overlays or a Google layer. You can find the code on github.

Did we miss something? You can contact us via weekly.osm@googlemail.com

Authors: Pascal & Dennis - (thx @ “Wochennotiz”)

Permalink

| Leave a comment  »

Written by admin in: News |

OpenMobileMap would not be possible without the generous support from our sponsors:

www.andgps.com provides gps and routing source code templates for android developers

www.j2megps.com provides gps and routing source code templates for j2me developers


OpenMobileMap | The Free Mobile Map Resources