Commentary

Ed Hansberry
 

Androids Returned More Than Other Gadgets

Just how high are return rates for the platform? One source stirs the pot.

High-tech gadgets often have higher return rates than things like toasters, socks, or tires. People get a new gadget and have buyer's remorse over the cost, find it doesn't do what they want, cannot figure out how it works, or just don't see how their life is easier than it was before parting with their cash. Some Android devices, though, seem to have a higher return rate than average for tech devices.

According to TechCrunch, some of the Android devices out there, which presumably covers tablets as well as phones, experience rates in the 30% to 40% range. That compares to a 1.7% return rate for iPhones, which I think seems a bit low for a tech device. That speaks to the simplicity, design, build, and power of Apple's device.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Now, you should temper this report with a bit of skepticism. The source isn't named and is listed only as "a person familiar with handset sales for multiple manufacturers." That is likely an analyst with information gathered from various sources, but that is only an educated guess.

Even if the numbers are double the true return rates, 15% to 20% is still high. It casts a cloud on the 500,000 daily activation numbers that Google tosses about. Cut that by 20% and the number drops to 400,000, which is still a lot of devices. Some of the returns are no doubt for hardware issues. All devices experience a certain failure rate, so someone returns a phone and swaps it out for a new one. This, too, impacts the activation rate as one person has activated two devices just to get one that works.

Part of the problem is expectations. Most people shopping for a smartphone know what an iPhone is, which is the standard by which all other smartphones are measured. They are either talked into an Android device or talk themselves into one under the premise that the phones are usually less expensive than an iPhone and they are as easy to navigate and use.

What happens is they find it isn't as simple, and it isn't even the same user interface as you move across different brands. HTC puts Sense on their Android phones, Motorola uses Blur or Droid on some of their phones, and Samsung has TouchWiz. Manufactures love to put their own custom user interface on a phone, thinking it improves it and makes it desirable. It often causes performance issues though, as is the case with the Droid 3. Even when the UI performs well, it may not be as well designed. No one would argue that these manufacturers have as much experience designing user interfaces as Apple has.

This means if someone looks at a friend's Android phone and likes what they see, there is no guarantee they will get the same thing if they go out and buy one, unless they get the exact same model. This no doubt contributes to a higher return rate.

I'll be curious to see if Google or its OEM partners refute this data with real return rates, or if they just give a collective "nuh-uh."


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links