Hello,

I think that the main reason why a device maker should allow an easy
replacement of the ROM is the generic and classical  "meet the users'
expectations" .

One of the selling point of the Android platform is the idea of having an
"open" operating system of mobile phones/devices . This means that many
users expect to be able to easily do upgrades, tweak the device, etc.  This
expectation is even greater for early adopters. And this expectation implies
having a "rooted" device.

So, given this kind of user expectations,  it is smarter for a manufacturer
to have an open attitude (allow non-standard rom updates,  involve the
community into developing the Android shipped with their device, etc... ) so
that the users can easily install various OS versions and applications that
require root permission.
If the user experience regarding upgrading the OS is nice,  at some point
the customer will reach the hardware limits and will be tempted to buy a new
more powerful phone so that he can enjoy the latest Android version.

In contrast, if the manufacturer wants full control over the OS installed on
their device and fail to provide the upgrades ON  TIME  they will only get
frustrated customers. Especially when the manufacturer is not capable to
provide the proper OS upgrades....

In my short experience the process of upgrading was a total mess :
Vodafone-branded HTC Magic, shipped with 1.5.  I wanted to try some
applications (AndNav2) that require 1.6.  HTC does not provide upgrades for
the carrier-branded phones.  And in my country Vodafone has absolutely no
intentions of providing those on-the-air upgrades:  there are people who
actually called the customer support and the vodafone staff had no idea
about the topic. So I was forced to read countless forum posts in order to
learn how to install a modified recovery that allows the installation if a
newer ROM.  First i tried a Cyanogen ROM that didn't work well (applications
crashing all the time). Now I'm running an AmonRa ROM that is ok.

This kind of upgrade problems are inacceptable. And the root of the problem
is that the manufacturers/carriers don't seem to understand the importance
of letting the users be able to use the full potential of the (expensive)
devices that they've purchased.

Seriously,  would anyone buy a PC if the manufacturer said  "this computer
works only with a Windows NT customized  by us especially for this PC. You
will not have administrator rights. The computer is locked and you, the
customer, cannot install any other OS.  In future we might provide free
upgrades. Or not.  But we'll probably produce exciting new models that will
include the coolest Windows version available at that moment."  ?

For a simple phone noone thinks about firmware upgrades or installing fancy
applications. The manufacturers are probably too used to this context. But
the smartphones are a different kind of beasts : these devices are in fact
computers with small touch screens. And it's not feasible to expect that the
users will be happy with rotting with whichever ancient OS version the
manufacturer cares to ship the device.



On Wed, Mar 3, 2010 at 20:30, Mark Murphy <[email protected]> wrote:

> I am in the process of collecting ideas from the community on one
> "simple" question:
>
> What are the *business reasons* why a device manufacturer should allow
> replacement firmware and/or root access by default on devices?
>
> The full post, along with some existing feedback, can be found here:
>
> http://www.androidguys.com/2010/03/03/reasons-root
>
> If you would like to provide input and would prefer to reply to this
> message rather than comment on the AndroidGuys post itself, cool! Here
> is what I am looking for (again, more details on that post):
>
> -- I want business and economic arguments, not moral or ethical ones,
> since we're long on the moral/ethical reasons and short on the business
> ones
>
> -- Act like professionals
>
> -- That being said, both carrots and sticks are valid suggestions
>
> -- Do not overestimate the size of the current modding community
>
> I will be rolling up the ideas into a follow-up post, and I hope to put
> these ideas to good use in the weeks and months to come.
>
> Thanks!
>
> --
> Mark Murphy (a Commons Guy)
> http://commonsware.com | http://twitter.com/commonsguy
>
> Android Online Training: 26-30 April 2010: http://onlc.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Android Discuss" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<android-discuss%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/android-discuss?hl=en.
>
>


-- 
Adrian M.

-- 
You received this message because you are subscribed to the Google Groups 
"Android Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/android-discuss?hl=en.

Reply via email to