Every Good Product Is Alike, Every Bad Product Is Bad In Its Own Way

You know the old Tolstoy line, "Happy families are all alike; every unhappy family is unhappy in its own way"? I think there should be a new variant for tech products: every good product is alike, every bad product is bad in its own way.

There is a simple rule in separating the bad from good. Good products make you want to use them. Bad products don't. The thing is, though, there are an almost infinitely large number of reasons *not* to use a product. Our surprise should be reserved for when we find ourselves driven to continue our engagement with a thing.

Marco Arment's review of the Kindle Fire is excellent evidence for this idea. He excoriates and details the dozens of little ways that the Amazon tablet doesn't work. Just his detailed review of the interface is quoted extensively below.

By contrast, if you were to describe the basics of iPad navigation, you wouldn't have to mention any of those things because the iPad interface works. The larger lesson: we note the specific ways something doesn't work, but when something does work, we just use it.

  • Almost the entire interface is sluggish, jerky, and unresponsive.
  • Many touch targets throughout the interface are too small, and I miss a lot. It's often hard to distinguish a miss from interface lag.
  • The on-screen Back button often doesn't respond, which is particularly frustrating since it's essential to so much navigation.
  • I keep performing small drags when I intend to tap, especially on the home screen. This makes the most common home-screen action -- launching something -- unnecessarily difficult and unreliable.
  • The load-on-demand images in various lists and stacks in the interface significantly slow down browsing: I scroll to a screen full of empty placeholders, then I have to wait for the images to pop in, then I can look for the item I wanted. (And then I can move on to the next screenful when I don't find it.)
  • Amazon's content-browsing apps don't respond well if lost internet connectivity is regained -- everything just sits there, empty, until you leave and re-enter that screen. This happens a lot when waking the Fire from sleep, when it has no connection for a few seconds before the Wi-Fi reconnects.
  • Once, I woke the Fire from sleep after only a few minutes of non-use and it rebooted for some reason. (I've only had it for two days.)
Presented by

How to Cook Spaghetti Squash (and Why)

Cooking for yourself is one of the surest ways to eat well. Bestselling author Mark Bittman teaches James Hamblin the recipe that everyone is Googling.

Join the Discussion

After you comment, click Post. If you’re not already logged in you will be asked to log in or register.

blog comments powered by Disqus


How to Cook Spaghetti Squash (and Why)

Cooking for yourself is one of the surest ways to eat well.


Before Tinder, a Tree

Looking for your soulmate? Write a letter to the "Bridegroom's Oak" in Germany.


The Health Benefits of Going Outside

People spend too much time indoors. One solution: ecotherapy.


Where High Tech Meets the 1950s

Why did Green Bank, West Virginia, ban wireless signals? For science.


Yes, Quidditch Is Real

How J.K. Rowling's magical sport spread from Hogwarts to college campuses


Would You Live in a Treehouse?

A treehouse can be an ideal office space, vacation rental, and way of reconnecting with your youth.

More in Technology

Just In