<i>There’s a distinction here between choosing and tinkering.</i><p>This is the crux of the argument. That choice is bad, and the people who like Android actually like tinkering, and don't really like customization, and it's just wrong.<p>I personally use my phone more than any other non-work device, and I love having it personalized to make everything I do often easy to access, and put everything else to the background.<p>I <i>chose</i> the best phone for me out of the very few real contenders on the market, I <i>chose</i> to replace my OS with Cyanogenmod, <i>chose</i> Nova Launcher, <i>chose</i> my layout and shortcut gestures, and <i>chose</i> my default keyboards as Google's English and Japanese keyboards. I haven't touched any of these for a couple of months, with the exception of replacing a couple of the gestures.<p>Phone usage differs a ton between individuals, and I'm glad I didn't lock myself into a one-size-fits-all solution.
Choice with reasonable defaults sounds ideal to me. The suggestion that you HAVE to make all these choices is FUD.<p>To bring a bit more consumer psychology into the discussion, people love SUVs because they give them the choice to go driving off-road, driving in snow, etc. Those SUV owners aren't then suddenly overwhelmed each morning with the question "Should I commute to work or should I drive to Tahoe?"<p>Android is a flexible tool that allows you to make choices when you want to make choices.
FTA: <i>I think many who extol Android’s flexibility fall into the tinkerer category, including some tech bloggers. [...] That’s fun for them; but they’ve made the mistake of not understanding how their motivation differs from the rest of us.</i><p>The problem with usability nuts and Apple nuts is that they fall into the "one perfect solution exists" category. That's fun for them, as they like their uniform devices just fine and get to write whiny blog posts about how all the other phones are Just Wrong. But they've made the mistake of not understanding how their motivation differs from the rest of us who like to have a deeper connection with our tools.<p>Yawn. Take all the fancy verbiage away and this is just another platform flame. Use what you like. Don't tell me how to use my phone.
To give a historical perspective, there was a similar issue with Unix OS's a while back.<p>You'd jump from a Linux box to a Solaris box, and things wouldn't work the same way? Simple things, like flags on "ps". Or, more seriously, the "shutdown" command (<i>shudder</i>).<p>That's only the CLI. Then you get into what Window Manager you're using, what desktop environment, etc.<p>Did any of this benefit the end user? In the end, most of this all ended up coming back to something that looks somewhat like OS X or Windows. A launcher bar and a menu bar, and maybe some status icons. Frequently ones that looked and worked exactly the same as OS X or Windows.<p>Fundamentally, all that choice didn't help Unix get market share. It hindered it. People didn't know what to expect, and wanted consistency. The same commands doing the same thing for the rest of eternity.<p>Incidentally, this also explains the Windows 8 backlash. I'm pretty sure that most non-technical people would prefer a innards-updated, security-fixed version of 8 that looks and works identically to XP.<p>In short, the problem is not choice, it's lack of consistency.
There is obviously a market for a phone with minimal choice, and it's filled nicely by Apple. I tend to agree that Android can be overwhelming, especially to new users, given the overwhelming number of choices, both critical and trivial.<p>In my opinion though, the solution is not less choice, but better and stronger defaults. There's no reason why android phones couldn't be as simple as iphones out of the box, but have more options for configuration for users who wish to dig deeper. Instead, at the moment we generally have phones full of bloatware, where many of the defaults seem designed to sell products and services of questionable value, rather than to aid the user.<p>The example of default application bindings in the article is a good one. That system is indeed terrible currently, but there's no reason it needs to be. At a minimum it should be possible to edit the bindings of any installed application, rather than simply clearing them all. (Right now it almost seems like the designers were trying to follow this philosophy of minimizing choice, but ended up with a hybrid that is both more overwhelming and less customizable than it could be.) There is also no reason why users necessarily have to be interrupted by the choice of app to perform a given action. Instead, an app could be chosen based on some predefined hierarchy, such as first installed. Then let the user <i>override</i> that choice if desired. (For example, by pressing the menu button within X seconds of one app launching another, then choosing the appropriate option.) You get the same benefit without overwhelming less knowledgeable users with choice. (And yes, some users might never realize that there was a choice at all, but that's a fair sight better than there indeed <i>not</i> being one.)
<i>think many who extol Android’s flexibility fall into the tinkerer category, including some tech bloggers. They love all the ways they can customize their phones, not because they’re seeking some perfect setup, but because they can swap in a new launcher every week. That’s fun for them; but they’ve made the mistake of not understanding how their motivation differs from the rest of us.</i><p>Everytime I hear this argument, I can only think that these people have developed a bad taste of Android and haven't used a stock experience for enough time. You don't <i></i>need<i></i> to tinker anything. The stock Android experience is a <i></i>good experience* by itself... but the option to tinker is there if you want it. If Apple made a car, the option to tinker wouldn't exist.
There's a problem with Android/Linux? Starting from a false premise
doesn't make for a good argument...<p>Assuming all Android devices would, could or should have the same
interface is like wishing all BSD-derived system were the same. Clearly
there's room for NetBSD, FreeBSD, DragonflyBSD as well as OS X and a
multitude of embedded systems?<p>If there weren't any differences between an LG phone and a Samsung phone
or a HTC product -- how would they compete? There <i>is</i> no Android
without (some) fragmentation.<p>Does this complexity cost (money, effort, q&a and developer time
etc...)? Certainly.<p>But to me the price is well worth it with the likes of the Cyanogen
project -- that allows all kinds of freedoms. For me personally it's
good -- but if I were in charge of developing some kind of system (say
handing out internal devices at a company) -- it's be much more
valuable. I'd be in control of upgrades and features. I could maybe
patch some minor issues myself. I could hold off on unimportand updates,
and rush those that affected my users. I can't see how you could both have
this, and at the same time avoid having a somewhat heterogeneous system.
I know Amazon agrees (look at the latest kindle tablet).
The problem with the argument is that it conflates choice with consistency. What every mobile vendor including Apple is principally attempting to do is to create a feature which a user will miss if they switch away, and for a lot of people Android wins because choice is a feature you'll lose or restrict on iOS.<p>I agree that a lot of time has been wasted by Android vendors on differentiation for differentiations sake. It's easier to superficially fuck with the UI than actually create a useful features.<p>I'm a great believer in Loss Aversion (<a href="http://en.wikipedia.org/wiki/Loss_aversion" rel="nofollow">http://en.wikipedia.org/wiki/Loss_aversion</a>) and Hotelling's law (<a href="http://en.wikipedia.org/wiki/Hotelling%27s_law" rel="nofollow">http://en.wikipedia.org/wiki/Hotelling%27s_law</a>) when it comes to device preferences.<p>These days I don't think many people are arguing that the iOS UI is significantly better than stock Android, Android has closed the gap or jumped beyond iOS depending on your personal preferences (Hotelling's law). Then consider how many people won't even consider iPhones because the screen size is too small (loss aversion).
It's not a bad thing that Verizon offers a slew of different Android phones and tablets with different features and price points. Choice is good. Choice is driving competition to create the best hardware to run android. Crappy hardware will fail, and good hardware will thrive.
For the context of this article I think there's a distinction to be made when it comes to choice and flexibility. Sure, when you go to buy an Android you're forced to choose. But when it comes to using an Android device a lot of decisions are made by default you just have the option/flexibility to change the behavior (ie there's a default keyboard but you can swap it out if you'd like). Ultimately I think the flexibility is a good thing, day to day with my Android tablet I don't feel bombarded with choices yet if there's something I don't like about it I'm more likely to be able to fix it then with iOS.
1. when i pick a launcher, i like to have 10,figuratively speaking, to choose from, not 1. i'll probably be using it for a long time..<p>2. i like the feeling. that if i ever need to change something, i probably can. its just a search away.<p>3. i like it that i can change things beyond even what the article was talking about if i wanted. e.g. say the if the silk browser was reviewed to be much faster than webkit/chrome/ff and i wanted to try it out on my lg phone..i can try...<p>4. 'choice' may even open up new functionality perhaps? does ios have llama/automateit/tasker equivalents?
Another issue with this article is it ignores a fundamental human trait that can be demonstrated through a number of consumer industries - people like choice.<p>While setting defaults in stone and never changing them might work if some people like your choices, being flexible has always been the greater path to success.<p>Witness the car industry, fashion industry, PC industry, etc... For better or worse, we like having alot of choices available.
What happens when the user downloads a PDF? Where does an app go after it is installed by the user?<p>These choices have to be answered one way or the other. The author of the article suggests that the company is better left answering these choices on behalf of the user.<p>Why would the company be better qualified to answer these choices over their users? That makes absolutely no sense to me.
there is also the choice in android to say no. I use a pretty stripped down android, only have one app for basically any given tasks. My intents screen never comes up with more than two choices for a task... It is possible to live a very full life on android without being drowned in options.