by Mike Masnick

Filed Under:
class action, nexus one

google, t-mobile

Google Sued For Nexus One Suckiness

from the people-sue-for-anything dept

Eric Goldman points us to the news that Google has been sued, in a class action lawsuit, over problems with the Nexus One, the Android phone (made by HTC) that Google released directly, in an attempt to get others to release better Android-powered phones. As with many new products, there were some bugs, and Google (and T-Mobile, on which the Nexus One worked) didn't quite know how to handle customer support for the device -- a pretty massive mistake. However, is it really against the law to sell a product with a few bugs and to to have really dismally crappy customer service? It seems like a stretch. You can make the argument that the product didn't do what was promised, but, like so many class action lawsuits, this one seems like a case of "gee, can we squeeze a bunch of money out of this company?"

Reader Comments

Subscribe: RSS

View by: Time | Thread

  1. icon
    Derek Kerton (profile), 13 Sep 2010 @ 11:17am

    Re: Market works how?

    Do you see a difference between a measurable metric like throughput, and a unknown metric like "number of bugs"?

    I hate crappy products, but if I joined a class action for every crappy tech product I bought, I'd be full-time managing my legal hobby, and I'd get hundreds of $5 coupons!

    The way to handle crappy products is to let the tech journalists chime in first. Which they did, as Google send them Nexus Ones before market release. Then bloggers like engadget or phonescoop get one and do tear-downs, detailed reviews. Then their comments fill with feedback from early adopters. Then bloggers do unboxings, early impressions, and evaluations. Then the dev communities push it to the limit, like XDA-developers.com.

    Bottom line, there is no need to buy a device like the Nexus One blind. If there were serious flaws, it would be identified as a dud long before the process above plays out. The market would react to the bad product. Um...Motorola Kin, anyone?

    If you want to make a list of Pros and Cons for a product, you probably shouldn't count on the seller to provide you the list of Cons.

    How about a little personal responsibility, a little caveat emptor, and a requirement to do a tiny bit of research before dropping $500 on a phone? Or should we just be able to rush in blind and let the legal system fix it if there are bugs?

    And, FWIW, I have an N1, and it is awesome. Of course, I never expected Google to answer the phone if I called, so I never did. If there was a 3G problem on T-Mo, which is a serious flaw, did Google fix it? How quickly?

Add Your Comment

Have a Techdirt Account? Sign in now. Want one? Register here
Get Techdirt’s Daily Email
Use markdown for basic formatting. HTML is no longer supported.
  Save me a cookie
Follow Techdirt
Techdirt Gear
Shop Now: Copying Is Not Theft
Report this ad  |  Hide Techdirt ads
Essential Reading
Techdirt Deals
Report this ad  |  Hide Techdirt ads
Techdirt Insider Chat
Report this ad  |  Hide Techdirt ads
Recent Stories
Report this ad  |  Hide Techdirt ads


Email This

This feature is only available to registered users. Register or sign in to use it.