How to ensure Gingerbread is sweet for all
For Android customers the process of getting an OS update can be tedious, confusing, frustrating, long winded and drawn out and its about to happen all over again. Earlier this week, Google announced the release of the SDK for Gingerbread, the 2.3 release of its Android operating system and stated that it will be rolled out in the near future.
Every time Google has announced a forth coming update to Android handset owners drool over the improvements they will receive. Anything from bug fixes, speed improvements to some serious additional functionality can be included in a release and so customers get whipped up into a frenzy eagerly anticipating how soon it will be delivered to their handset. The problem is, there isnt an easy answer to this question. Well it seems there isnt but I must be missing something as its quite simple really
The problems:
There are now many different handsets from numerous manufacturers that run Android. All these handsets are not considered equal when it comes to an update.
Some are much older and may not have the required spec to run the latest release.
Others are classed as “Comes with Google” handsets which means they have a pure untouched, straight from Google version of the OS with no additional UI or skin over the top.
The remainder and bulk of the handsets carry additional ‘skins’ such as HTC’s Sense UI or Motorola’s Blur interface for example.
What this means for the customer:
The process is not ‘One process fits all’, if and when they are to receive the update varies dramatically. The content of the update may also be very different. Some MNO’s use the opportunity to bundle in some of their own applications in to the updated e.g. Vodafone’s 360 applications those with handsets for some manufacturers will get an update to their UI.
Communication is very poor from all companies involved leaving the customer confused, frustrated and very vocal on their discontent.
What this means for the Mobile Operator
Mobile Network Operators seem to be the first people that customers turn to as it is MNO’s that have sold them a handset and a costly monthly contract. This causes big problems as the MNO’s are pretty much stuck in the middle getting all the grief from customers and very little help from manufacturers and Google in terms of hard and fast deadlines when updates will be pushed out.
MNO’s dont help themselves though, as their communication leaves alot to be desired. Funny how companies that have made their fortune from communication cant even agree a statement internally and stick to it. Instead many confusing messages are passed out to customers across numerous platforms leading to an uproar on forums all over the web.
The solution:
Agree a strategy internally of how the update will be rolled out.
Speak with handset manufacturers and Google and agree which handsets will receive the updates and when in terms of month or at least quarter.
Communicate to all Android handset owners whether they will or will not receive the update.
If they will receive the update give them an indication of timelines.
Included in the communication and published on numerous channels should be the process in terms or roles and responsibilities of all the parties involved from Google, the manufacturers and even the customers. Write it in plain English and point everyone at this message.
Sounds simple doesnt it? Bet it doesnt happen.
My Understanding of how it works today
Google releases the SDK, at which point handset manufacturers and mobile operators all take the code to review, test and build on in the case of those that produce UI’s.
Any unlocked devices that ‘Come with Google’ i.e. a clean version of Android, get the update before anyone else.
Comes with Google devices that are locked i.e. those sold with a contract from a mobile network operator (MNO) will get their update once the MNO in question has tested the update and approved it.
Those with an unlocked handset with a skin / additional UI developed by the handset manufacturer will have to wait longer whilst the UI is updated. The manufacturers tend to start with the most recently released handsets and work backwards, e.g.customers with an HTC Magic are still waiting for Android 2.2.
Then there are those people who have an older unlocked handset may not even get the update at all.
Those with handsets locked to a mobile operator have to wait and watch on with green eyes as those with unlocked devices get their updates. The mobile operators have to approve any software roll out so even if they have a ‘Comes with Google’ handset, there will still be a delay over unlocked devices. Those with handsets with additional UI’s will have to wait further still as the MNO will have to approve the additions and as already mentioned, add in and or update their own applications before allowing the rollout.



![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=404ce212-80bf-4082-bd96-38ce626534f1)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=a387f902-2549-4e27-b1b4-9f45aad0ae5a)