Slashdot Mirror


Is Choice a Problem For Android?

New submitter mjone13 writes "Dave Feldman, in a blog posts, says that the problem Android faces is giving consumers too much choice. He cites several studies which state that consumers generally are unhappier when they have too much choice. 'Catering to all individual preferences creates a bloated, bland product. Not to mention a UI that’s impossible to navigate. Furthermore, people are notoriously bad at identifying what we want. And what we do want is influenced heavily by what we know — our expectations are constrained by our experience.' He then goes on to talk about Android fragmentation, app developer problems and bug issues. Finally he says the people who general prefer the choice Android provides are tinkers similar to gear heads who love tinkering with their car. '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.' Is choice really a problem for Android?" Whether it's a problem depends on what the goals are. Providing a satisfying experience to a bunch of tinkerers is a very different thing from providing a satisfying experience to the multitude of non-tinkerers who buy smartphones.

15 of 361 comments (clear)

  1. choice doesn't *require* bad defaults by Trepidity · · Score: 5, Insightful

    You can have a highly customizable UI without making the default bland and impossible to navigate. Having more customization does make some things more difficult, since you can't assume all users will have the same setup, but it's still compatible with a decent default interface.

    1. Re:choice doesn't *require* bad defaults by somersault · · Score: 5, Informative

      Why is everyone talking like there even is a problem? In August Android had almost 80% of the market. Yeah, it must be incredibly boring and horrible to use if so many people want it.

      --
      which is totally what she said
    2. Re:choice doesn't *require* bad defaults by jareth-0205 · · Score: 5, Informative

      It's not the users that are the problem its the dev teams because if you're writing for Apple you only need to test on few handsets & tablets. However, if you're writing for Android you need to test on fucking hundreds of different hand sets because each manufacturer has fucked with the OS. So either apps don't get written for android or if they do they normally get approx 100th the testing apps get on Apple.

      Except if you were actually a developer working in the real life world (I am, on an app with 2 million daily active users) you'll know that that is not at all necessary. There are device-specific bugs, but they're rare, and in the most part we rotate testing on about 6 devices, and use bug reporting libraries to catch the rest. Our crash-rate is a tenth of the iOS team's crash-rate.

    3. Re:choice doesn't *require* bad defaults by LordThyGod · · Score: 5, Insightful

      Why is everyone talking like there even is a problem? In August Android had almost 80% of the market. Yeah, it must be incredibly boring and horrible to use if so many people want it.

      Exactly. Its like the fragmentation argument that is just killing Android. Or how insecure Android is. Its just people writing headlines to attract attention to themselves.

    4. Re:choice doesn't *require* bad defaults by master_kaos · · Score: 4, Interesting

      I do development for ios and android. 85% of our downloads are on apple, 15% on android. We are a small shop so we are not going to go out and buy every device to test it on. Generally our apps are ok with most android devices, but there will always be one specific type of device that the app will crash on because it does something a little differently.

      Not to mention all of the different versions, you have people running everything from 2.1 to the latest version. For our app on android 63% are running 4.0.3+, however 31% are running 2.3 so we can't abandon 2.x yet. With iOS you generally only care about previous version. So currently target for 6.1 or higher, if you REALLY want to squeeze out every last download stat you can, aim for 5.1 (since ipad 1 can't upgrade to ios 6)
      http://david-smith.org/iosversionstats/ I find these statistics fairly accurate. Since we don't use any ios6 features we target 5.1+.

      One of my cousins is a product manager at a medium sized mobile gaming company, he said they have a similar experience to ours. Their games download stats are about 10-20% android rest iOS, yet they spend 3x the resources on android support as they have about 90 devices laying around to test on, and people always calling up because "it runs slow on this device", "it crashes on this device". They completely killed android development except for their top couple apps

    5. Re:choice doesn't *require* bad defaults by Russ1642 · · Score: 4, Funny

      Makes me think there's a tech-journalist troll-list that rotates with standard topics.

      It's called Slashdot.org

    6. Re:choice doesn't *require* bad defaults by ducomputergeek · · Score: 4, Interesting

      A lot depends on who and what you are targeting. If eyeballs and advertising is what you after supporting Android is a must. But if you are after in-app purchases as your revenue model, it's iOS you want.

      I've been developing mobile apps since 2009. Early on I was making as much off ad revenue vs app purchases, but by last year the ad revenue went in the crapper. So much so that I stopped releasing updates for android. By that time Android accounted for a little over 60% of the installs. It accounted for less than 15% of my revenues. Android accounted for over 90% of my complaints and requests for support because someone with a cheap pay-as-you-go android phone would run into a problem on a device I didn't even know existed. I was making at most a couple thousand a month from the apps, mostly from iOS users. It was enough that it paid my basic living expenses like rent & utilities meaning my day job work could go into savings. But it wasn't enough for me to go out and buy every freaking handset on the market at $600 a pop.

      Now on the professional day job part of the world we usually price for iOS first and includes QA for current generation and usually the previous 2 generations before that. Right now if you paid us to write an app, we'd ensure compatibility with the iPhone 4, 4s, 5 & iPad 2, Retina, Mini. Next month it will likely be 5S/C, 5, 4S & iPad Retina, Mini, + whatever is announced next week.

      For Android we will test against Nexus Phone & Tablet and certify QA with those devices only and it costs our clients about 1.5xiOS. Why? Because we know we'll be answering "QA for XYZ handset was not covered in the contract" a few times. So we build it into the price of the contract. We do offer QA for additional handsets & tablets @ $5,000 per Android handset/tablet. Most of our clients will maybe ask for QA against the latest Samsung Galaxy devices and that's it. Only one that I can think of asked for Samsung & Motorola because the boss man had a motorola phone.

      When Android first started we tried to QA against as many handsets as we could and we were losing money on those contracts. When Google released their official devices we decided, even though nobody used them in the mass market, those would be what we'd test against. That was the "official" devices for compatibility. What handset makers & carriers did beyond that we'd have to charge extra to fix because we'd run into the same model android phone would have odd quirks between different carriers sometimes.

      --
      "The problem with socialism is eventually you run out of other people's money" - Thatcher.
  2. SubjectsInCommentsAreStupid by lesincompetent · · Score: 5, Insightful

    I stopped reading at "Not to mention a UI that’s impossible to navigate."
    My bullshit detector went off the scale.

  3. Not all choice is tinkering by samael · · Score: 5, Insightful

    Some of us get their phone, install it the way _we_ want it, and then leave it like that (unless something spectacularly new comes along).

    I don't change my keyboard weekly - but I did change it a couple of times, find one that suited me, and leave it that way.

    Same with SMS, email client, and web browser. I haven't changed any of these in months, but they're all different to the stock version.

  4. Re:what I want to say is, by gl4ss · · Score: 5, Informative

    "Dave Feldman is a product designer with a background in user experience, product management, and front-end development. Heâ(TM)s the co-founder and chief product officer of Emu. Heâ(TM)s held positions at Yahoo! and AOL. Check out his website Operation Project and follow him on Twitter @dfeldman."

    aka mr. "I configured my configurable system to act like crap and by the way I love iPhone".

    now, of course if I can make a plugin to handle file saving.. then of course I can install a dozen apps to do it. just because I install two different homescreens for example doesn't mean that I have to choose between the two each time I press home.. I could though, if I wanted.

    basically the answer to his problems is to not install extra apps. I don't know what the fuck is his actual suggestion on how to remove the problem of choice. maybe he is working on his own android variant where you can't install anything... more likely he is trying to troll some buzz and score a new gig. that's what his writing looks like. only made more obvious by him submitting these pieces on different blogs to gather maximum buzz since nobody gives a shit about his blog and the product he is promoting(emu.is, some kind of sms frontend where you can attach your position easily. how novel, for 2003).

    and the other problems? android phones are so BIG! well fuck buy a smaller android phone.

    (oh and he doesn't really seem to understand android multitasking, only sort of).

    --
    world was created 5 seconds before this post as it is.
  5. Just a click-bait using a old-ass argument by aiadot · · Score: 5, Insightful

    Seriously that is all I see in this article. Flaming for the sake of clicks/views. Android fragmentation was a problem back in the version 1.5~2.1 days. Back when OEMs were experimenting and the software was maturing. Nowadays, save for a handful of tweaks, all decent Androids devices are pretty much equal. As for the UI tools, maybe not having tons of options will make that guy happy, but removing them will make a lot more people angry. What does he want? A Google branded iPhone?

    Even though I subscribe to the Apple/BlackBerry/GameConsole idea of one optimal OS for one or two device types, I'm still mostly a windows and android user. Trying to make everybody happy with the "one OS for them all" strategy is just impossible plus there are many marketing and development problems associated to it for platform providers, OEMs, developers and users. However to say that the Android(and by extension windows) experiences are crap, is pure BS. Like it or not, Android gets the job done, and the experience is without a doubt what I would call very reasonable . At least that is from my experience with Galaxy and Xperia phones as well as a Transformer Tablet. If you got a $0 chinese phone with a shitty firmware that is your problem, not Android.
    Sure if I could get my way, each company would have it's own OS and ecosystem, assuming that all tech companies had a interesting and unique vision for themselves. Too bad that is just unrealistic plus there are plenty of practical problems associated to this philosophy as well, but that is a discussion for another time.

  6. Choice ? by giorgist · · Score: 4, Insightful

    Android offers choice only to tinkerers. Everybody else simply walks in a store and buys a phone that looks shiny. iPhones are having a bit of a problem in that they offer almost a single choice which was the same as that from a few years ago. You can't have a bigger screen for example. Mobiles have achieved appliance status. Who cares about fragmentation ? There is fragmentation in car models as well and fancy cars that have weird ways to switch on. After you master it, you run with it for years. You don't care if the car in the opposite traffic works differently. Fragmentation affects developers, who now have massive budgets to overcome it. There are hundreds of thousands of apps, most people use only a few and the rest they simply forget to delete after they are downloaded. So there are enough that work well out there.

  7. Basically, no. by Cloud+K · · Score: 4, Insightful

    The reason I switched from iOS was because personally, I *want* control over my smartphone. I want the options and customisations, and the ability to decide what keyboard to use and where my music sits. My advice to those who can't handle a few options is "get an iPhone".

    Though really, I can't see why both user groups can't be catered for - have sensible defaults and basic options, and put everything else inside an "Advanced settings" button somewhere - no one is forced to tap it.

  8. Somewhat lacking in logic. by GrpA · · Score: 4, Funny

    The problem that the PC faces is giving consumers too much choice....

    Clearly that hasn't worked for the PC, or it would be the 100% dominant platform, rather than just the 99% dominant platform...

    And for PCs the be able to run OS-X, Microsoft or Linux operating systems? Clearly wayyyy to much choice...

    GrpA.

    --
    Enjoy science fiction? "Turing Evolved" - AI, Mecha, Androids and rail-gun battles. What more could you want?
  9. Irony by tuppe666 · · Score: 5, Insightful

    To be fair, Android is harder to navigate. There are desktop pages (similar to IOS app pages). Then there's a list of apps under the apps button. You can also copy stuff from the apps list to the desktop list.
    I find this paradigm very confusing. I've seen Android users get confused on this too.
    But, I desperately miss configurability in IOS. Absence of settings has my life very hard in the past... So has the conduit called iTunes. iTunes really sucks when it doesn't work properly, and is clunky when it does work.

    Itunes is a nightmare that should have been burned with fire, on Android you do not have this extra layer of complexity at getting content onto your devices.

    You talk about reconfigurability and settings...or the absence of them. Ignoring the irony of arguing for additional complexity at the cost of customisability, or that Apple copied the look of this with iOS 7 from Android, you argue that having a desktop(sic) that you can only add applications to is better than one you can add widgets to.

    I don't think you really understand your own argument.