Skip Links

Network World

Mark Murphy

Android Device Makers: Ask, And Ye Shall Receive

Use the Community to Help Build a Better Product

By Mark Murphy on Wed, 08/19/09 - 9:10am.
Newsletter Signup

The T-Mobile G1 has had storm clouds over it since shortly after its introduction, mostly stemming from on-board storage. Initially, the complaints were targeted at lack of space for installing third-party applications. Now, the complaints are lack of space for the Android OS itself, which at some point will mean no more Android updates for that device.

Those complaints are no doubt annoying to HTC, T-Mobile, and others. The community at present is incapable of understanding the design trade-offs that go into making a device, because the community lacks all of the information. There may have been very good reasons for limiting the on-board flash, from cost constraints to parts availability to simple miscalculations.

One lesson that device makers should take from this episode is that the community can be rather noisy. It is not uncommon for memes to be started in blogs and jump to more mainstream media, extending their visibility. This is far from unique to Android, of course.

Some firms may take the angle of trying to avoid the public. This works, so long as you are not trying to sell anything. Since most firms sell things, eventually the public winds up face to face with the products, if not the firm, and the complaints will simply begin then.

An alternative approach is to try to engage the community early on. Give the community a sense participation, and you may be able to stem some of these complaints. Unfortunately, all too often, firms try to get input too late, or from too few people, or with too many pages' worth of NDA limiting the community's chances for input. But it doesn't have to be that way – after all, if you can crowdsource finding veins of gold ore, you can probably find ways to crowdsource major device features.

For example, offer up a budget-style survey, where participants can allocate points among a series of device criteria. Some criteria may be expensive (e.g., 100 points apiece for “extra memory for firmware, to perhaps extend the number of OS upgrades” and “extra memory for third-party applications”), and some may be cheap (e.g., 20 points for “ships with useful case”, 5 points for “artistic laser engraving on battery cover”). Voters only get so many points, insufficient to vote for everything, so they have to make decisions. This serves two purposes:

  1. You gain useful opinions, to gauge interest in various capabilities, which might steer product decisions
  2. Those who participate in the survey start thinking about implementation trade-offs, hopefully realizing that for everything they want added (e.g., more OS updates), something else has to be traded away (e.g., more space for apps)

The community is oblivious to the design decisions that go into device manufacturing. If you want better criticism of your decisions, give us structured ways to provide such criticism, early and often. We are your consumers and your biggest source of fans. We are not the enemy, even if some days we might seem like it.

Allow Memory Customization

0

Perhaps allowing these phones to swap / expand internal memory would make devices truly open.

Obviously the device makers want some planned obsolescence so you buy their next phone, but providing a memory upgrade ability could be a differentiator in the market & another money maker by selling the memory upgrades itself.

Same with swapping out processors just like with PCs but obviously the hindrance is the much smaller scale & idiot proofing it.

,Michael Martin
Google And Blog

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • You can use BBCode tags in the text.
  • Lines and paragraphs break automatically.
  • Allowed HTML tags: <p> <strong> <i> <br /> <br> <ul> <ol> <li> <dl> <dt> <dd> <blockquote>

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Welcome, visitor. Register Log in
About Android Angle
Mark Murphy is the founder of CommonsWare and the author of The Busy Coder's Guide to Android Development. A three-time entrepreneur, his experience ranges from consulting on open source and collaborative development for the Fortune 500 to application development on just about anything smaller than a mainframe. A polished speaker, Murphy has delivered conference presentations and training sessions on a wide array of topics internationally. Outside of CommonsWare, Murphy has an avid interest in how the Internet will play a role in citizen involvement with politics and government.