Why My Mom Bought an Android, Returned It, and Got an iPhone | Betabeat — News, gossip and intel from Silicon Alley 2.0.
From the second we turned it on, the user experience was astonishingly bad. Want to activate your phone? Take the battery out, write down a series of minuscule numbers that you find on the phone and on the SIM card, then enter them into Verizon’s barely-functional site. Once you’ve got it hooked up, navigate the opaque first time setup, if it doesn’t crash while you’re entering your information (it did – twice). Once you’re done with the setup, enjoy the apps that Verizon and Samsung think you should use: a terrible golf game, a Samsung branded Twitter client, Verizon’s half-baked navigation app.via Why My Mom Bought an Android, Returned It, and Got an iPhone | Betabeat — News, gossip and intel from Silicon Alley 2.0. What's the new user experience for your products? Does it work great right out of the box, or is your customer forced to mess with the installation to get a working solution. This article focuses on the disaster for one model of the Android phone while referencing a delightful experience with another model. And that's one of the challenges of that space: the carrier interferes between vendor and user, adding their pointless crap. Stuff neither the vendor nor the user wanted. In their effort to "have more features" (or a more branded experience perhaps), they have added difficulty and complexity--and destroyed the user experience. Many products do 70% of everything; the great ones do 100% of some things. Which is yours? (PS. This isn't an operating system rant. It's about user experience and getting the feature set right).
Looking for the latest in product and data science? Get our articles, webinars and podcasts.