Linked by gsyoungblood on Tue 20th Jul 2010 18:01 UTC
PDAs, Cellphones, Wireless On July 15th the latest Android super-phone was released by Motorola and Verizon Wireless. All hail the Droid X. The release was not without controversy though. The Droid X, while greatly raising the bar for Android phones in general, does so at the expense of the very power users and community that made the original Droid the gotta-have phone it became. Alienating this group may have far reaching consequences for Motorola.
Thread beginning with comment 434251
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Comment by moondino
by aesiamun on Wed 21st Jul 2010 19:24 UTC in reply to "RE[4]: Comment by moondino"
aesiamun
Member since:
2005-06-29


Because if they block non-authorised ROM installations, these custom ROM implementations become popular, as a developer your potential customer base shrinks because of it. I would have thought it was pretty obvious.


Why block custom rom implementations? Just say up front that this is not supported under custom roms...blocking is a terrible way of garnering any support.

And that, I would have thought, was a pretty obvious move.

Edited 2010-07-21 19:24 UTC

Reply Parent Score: 3

RE[6]: Comment by moondino
by kaiwai on Wed 21st Jul 2010 23:37 in reply to "RE[5]: Comment by moondino"
kaiwai Member since:
2005-07-06

Why block custom rom implementations? Just say up front that this is not supported under custom roms...blocking is a terrible way of garnering any support.

And that, I would have thought, was a pretty obvious move.


The Android Marketplace might block them but Android doesn't stop you from manually loading the applications outside of the Android marketplace. They block it because if something goes wrong then the carrier, application vendor, or Google is hounded by the person with the custom ROM. It is up to the software vendor to sell through the Marketplace, outside the Marketplace or both.

Reply Parent Score: 2