Slashdot Mirror


Eric Schmidt Doesn't Think Android Is Fragmented

adeelarshad82 writes "Eric Schmidt took issue with the idea that the Android mobile operating system is fragmented, arguing that it's a differentiation between devices rather than a fragmentation. The difference, as he explains it, is that differentiation means manufacturers have a choice, they're going to compete on their view of innovation, and try to convince consumers that their innovation is better than somebody elses whereas fragmentation is quite the opposite. Not surprisingly, some company analysts beg to differ, pointing out the ever increasing incompatibilities between OS and apps across different Android devices and other problems with Android."

87 of 431 comments (clear)

  1. Eric Schmidt, master of non-answers by bonch · · Score: 3, Interesting

    Manufacturers competing on their "view of innovation"--which apparently means junkware like TouchWiz--is precisely what is fragmenting the platform. Schmidt seems to believe that by reframing it with a feel-good word like innovation, he can successfully claim that it's somehow the opposite of fragmentation. The differentiation and and in-fighting between manufacturers and devices is the fragmentation. Nothing he stated refutes the claim that the platform is fragmented; he's just describing the fragmentation in a different way.

    NPD now says that iOS has officially closed the gap with Android in U.S. marketshare since the release of the iPhone 4S, so these issues are having a real effect on the platform. According to NPD's report, 150 Android handsets can't beat three old iPhone models. What's happening here is that Android phones catered to techies and budget buyers, but with the iPhone 3GS now free on contract, Apple now has budget buyers covered--and there are way more of them than there are techies.

    1. Re:Eric Schmidt, master of non-answers by jedidiah · · Score: 3, Insightful

      I dumped my iPhone for an Android.

      Clearly my use of a phone is too "geeky".

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:Eric Schmidt, master of non-answers by SJHillman · · Score: 3, Interesting

      I paid $160 for my LG Optimus Slider from Virgin Mobile. For my use, the only thing that works poorly on it compared to an iPhone is NetFlix, which tends to have choppy video. However, it has a physical keyboard, which more than makes up for not being able to watch tiny movies in my opinion. I also find the Android interface to be somewhat more intuitive than IOS (at least in most cases). Also, everything I can't do on my Android phone, I can do on my $180 Nook Color. So for $340, I can do everything I would want with an iPhone and a whole lot more. Having it split between two devices is actually more convenient for me as I take the phone with me everywhere but I rarely use the Nook (mostly for Netflix and books) outside of home.

    3. Re:Eric Schmidt, master of non-answers by hedwards · · Score: 4, Informative

      There is no fragmentation problem with Android. It's always been something that Apple fanbois have used to attack Android for being less homogenous. The fact though is that Google provides the tools for developers to handle the variations in screen size and such and in practice developers don't seem to be having too much trouble with the fragmentation issue.

      True early on some features wouldn't be supported on older versions of Android, but the same is true with iOS, Apple adds new features and doesn't necessarily port them to old iPhones.

    4. Re:Eric Schmidt, master of non-answers by Baloroth · · Score: 5, Insightful

      Oh wow shocking, Apple gained sales market share right after releasing a brand new super-hyped phone and lowering their old prices! Android is doomed! DOOOOMED, I tell you!

      Anyways, fragmentation is good for the market. Allows for true competition and drives features. The newest Android phones are far and away more featureful than any iPhone, plus you can choose from any carrier and any range of features you want. I would have liked Google to encourage manufacturers to release more updates to their phones so people didn't get stuck on 2.1 or whatnot, but the fact that most Android programs work on most Android devices is nothing short of amazing when you think about the vast array of different hardware they can contain.

      --
      "None can love freedom heartily, but good men; the rest love not freedom, but license." --John Milton
    5. Re:Eric Schmidt, master of non-answers by tripleevenfall · · Score: 5, Insightful

      But per the usual misunderstanding on /. , the general public is not geeky. It does not use hacks or cracks, it does not sideload or use custom ROMs. Most don't even upgrade the SD card, or even know that you can.

      The general public picks a phone up and evaluates it, if they evaluate it pre-purchase at all, based on a 1-5 minute poking around on the device. I think the iPhone wins these battles with the average, uninformed consumer because the graphical presentation is slick and the interface is intuitive to the non-techie.

      Some people equate smartphone with iPhone. For those who don't, most of them will buy whatever gives them the cleanest presentation and seems easiest to use. Openness and Google and other geek-factors don't enter into it.

    6. Re:Eric Schmidt, master of non-answers by tripleevenfall · · Score: 4, Insightful

      My experience has been a little bit different, I used an Android phone for about 2 years and now use an iPhone. I can't name any app that is better on Android. Sometimes they are roughly equivalent, sometimes they aren't, but what is usually the case is that the iOS version is smooth graphically, opens/closes without fits and starts, doesn't creak when interrupted by calls or texts, etc etc.

      A good example is the ESPN Scorecenter app. the iOS version is great. The android version is more simplistic graphically, it doesn't wipe or update as well... for me, sometimes it needed to be killed and restarted to update scores.It works well enough, it's just not as polished.

      It's probably not the developers' fault, I think there is universal agreement that Android is much harder to develop for. This works itself out in app quality.

    7. Re:Eric Schmidt, master of non-answers by Missing.Matter · · Score: 3, Informative

      Only on price though. Android runs terribly on low end smartphones and don't even have the full feature set of a top of the line android phone. Further, they're likely to be abandonded, perpetually running an outdated version of android until you ditch it. With the iPhone, even buying last gen you're getting most of the features of the top of the line. The WP7 Samsung Flash costs .99 on AT&T and offers the same exact user experince as a top of the line WP7 phone. So why is anyone ever choosing low end android phones? Because 1) the carriers are pushing them since they know they don't have to provide expensive upgradde support and will rope customers in for another contract since the phone will never be updated and 2) there's a lot of buzz around "Android" and people think even the low end phones will deliver the same experience, when what they get is a slow, feature-barren, "smart phone" that was abandonded by the manufacturer the second it shipped.

    8. Re:Eric Schmidt, master of non-answers by fightinfilipino · · Score: 3, Informative
      i just picked up a Samsung Galaxy S2 skyrocket and a 32gb minisd card for a grand total of US$200. that's a total of 42gb in storage space (the phone has 10gb internal storage), along with a very fast dual core processor and, more important, actual 4g LTE capability.

      in comparison, Apple's 32gb nonexpandable iPhone 4s is $100 more, has a weaker processor, and is stuck with 3g speed.

      i don't consider myself a full android fanboy, but based on these facts alone, you can get MUCH better android devices for far cheaper than a handicapped iPhone.

    9. Re:Eric Schmidt, master of non-answers by tripleevenfall · · Score: 2

      Does the same criticism not apply to the HTC/Samsung/etc which you're paying for over the life of the contract?

      Would you not be paying the same monthly rate, whether you purchased the device outright or not?

      From a certain point of view, if you're going to be paying the same monthly rate for 2 years of a data plan, you may as well be getting a free phone vs. nothing in return.

    10. Re:Eric Schmidt, master of non-answers by Anonymous Coward · · Score: 5, Interesting

      The fact though is that Google provides the tools for developers to handle the variations in screen size and such and in practice developers don't seem to be having too much trouble with the fragmentation issue.

      I'm just finishing up my first Android app. It's a simple app, yet several times I've already needed to use reflection to dig around in undocumented APIs or roll my own version of a class included in the framework because of differences between the API versions. I have also found that it is difficult to add functionality to framework classes because Google makes many of the methods either private or final.

    11. Re:Eric Schmidt, master of non-answers by neokushan · · Score: 3, Informative

      I know plenty of the "general public" who aren't geeky but love Android phones. I know even more that love phones which happen to be Android phones, all former iPhone owners.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    12. Re:Eric Schmidt, master of non-answers by Anonymous Coward · · Score: 4, Funny

      Oh sorry, I was busy playing my superior games and using my wider selection of apps, to care that your phone has more numerical specs than mine. Geek bias.

    13. Re:Eric Schmidt, master of non-answers by Missing.Matter · · Score: 5, Insightful

      Apple adds new features and doesn't necessarily port them to old iPhones.

      Apple is pretty good about updating their product line to the current OS. True, you're not going to update your original iPhone to iOS5. But you're not going to buy a brand new last gen iPhone 4 or even iPhone 3GS with iOS 3. Same with Windows Phones, they all currently run the latest release of WP7, even if you buy a last gen samsung focus from. However, in the Android world you can buy a brand new Android phone with an OS 2 versions out of date, and that phone will never be upgraded. THAT is the problem. We're not talking about 4 year old phones not getting the latest release. We're talking about brand new phones that are out of date, out of the box. This isn't a fairy tale.

    14. Re:Eric Schmidt, master of non-answers by Anonymous Coward · · Score: 3, Insightful

      Yet you will still run into choppiness and various performance issues with that faster processor. I have yet to see an Android system that runs as crisply and smoothly as an iPhone. It's probably due to all the things that can run in the background (crapware + whatever else), on top of the Linux kernel's questionable scheduler, which dogs desktop machines as well. And let's see if you're still running the latest Android firmware a year from know. Even iPhone 3GS's were instantly upgradable to iOS 5 the second that Apple announced it.

    15. Re:Eric Schmidt, master of non-answers by wzinc · · Score: 3, Insightful

      With iCloud, my whole 80+ GB collection of music and movies is with me wherever. Phone storage doesn't matter.

    16. Re:Eric Schmidt, master of non-answers by nahdude812 · · Score: 5, Interesting

      The target demographic for smartphones is geekier than the average public. Most geeks have smartphones, for example. Teenagers and young adults regularly defy the traditional concept of "too geeky" or requiring too much effort for the "average" person, and these same are also among the prime candidates for smart phones.

      Nonetheless, "fragmentation" is a marketing term being bandied about by Apple apologists. It's an excuse to justify a technology monoculture that Apple has established in some corners of the market. Technology monoculture has invariably led to technology stagnation.

      Rather than "fragmentation" being a bad thing, what's actually going on is "innovation," and that's a good thing. People didn't talk about desktop fragmentation in the PC era, people don't talk about console fragmentation when you need specialized controllers to interact with many of today's games.

      This is survival of the fittest. My wife is a complete non-geek. She traded out her iPhone for Android and is eager to ditch her iPad. The sole reason being that she wants to consume content which requires Flash. She's not interested in assertions that her life would be better if only websites would ditch Flash, she's interested that her technology can't do the task she wants it to.

      Technology monoculture is the real problem here. iOS suffers from it, while Android doesn't. Android should wear this term with a badge of pride; they are currently steadfastly half way between steps 2 and 3 (out of 4) in Gandhi's famous quote about winning. They were ignored (Android 1.x era), they were laughed at ("fragmentation"), now they're being fought (Apple v. Samsung for example). Only one more step to go.

    17. Re:Eric Schmidt, master of non-answers by sourcerror · · Score: 2

      " It does not use hacks or cracks, it does not sideload or use custom ROMs."

      You can bet they use shitload of cracked software in Asian and Eastern European markets, no matter what device (PC/game console/smartphone). I don't think that in these places iOS is competitive with it's walled garden philosophy (i.e. they still want warranty).

    18. Re:Eric Schmidt, master of non-answers by bkaul01 · · Score: 4, Insightful

      I agree that the general public is not geeky, but if their purchasing were primarily based on having a slick graphical presentation and intuitive UI, the new Windows Phone should be winning hands-down. Most of the general public, I'd posit, is heavily influenced by Apple's slick marketing, and a large number buy whatever the salesman at the retail store pushes (which is largely based on sales incentives or his own fanboyism), or what their friends and family recommend.

    19. Re:Eric Schmidt, master of non-answers by karolbe · · Score: 3, Insightful

      Really?? I have Samsung Galaxy S2 and I can't recall any incorrectly working application, and I have downloaded a lot. Guess I am (again *) lucky ;-) (*) - the same is with my Linux PC, in last 2-3 years never had any issue with drivers, non working devices etc.

    20. Re:Eric Schmidt, master of non-answers by Anonymous Coward · · Score: 5, Insightful

      My experience has been a little bit different, I used an Android phone for about 2 years and now use an iPhone. I can't name any app that is better on Android....

      Google maps. Navigation specifically. Voice navigation more specifically.

    21. Re:Eric Schmidt, master of non-answers by Galestar · · Score: 5, Insightful

      Android actually reduces fragmentation. Could you imagine what would happen without Android? Every phone manufacturer would have its own completely different OS. If Apple MS and RIM threw in the towel today and all switched to Android there would be significantly less fragmentation in the marketplace as a whole.

      The argument that Schmidt is making - manufacturers need to be able to differentiate their products. Android allows them to do this without sacrificing interoperability on the scale that Apple/RIM/MS sacrifice it.

      You - bonch/Overly-Critical-Guy - live in a closed bubble where all you can see is "Apple good, Android bad". You have blinders on your eyes. Please either take them off or stop posting.

      --
      AccountKiller
    22. Re:Eric Schmidt, master of non-answers by SplashMyBandit · · Score: 4, Interesting

      I'm just finishing up my first Android app. It's a simple app, yet several times I've already needed to use reflection to dig around in undocumented APIs or roll my own version of a class included in the framework because of differences between the API versions. I have also found that it is difficult to add functionality to framework classes because Google makes many of the methods either private or final.

      Good luck with that app. Yes, unfortunately many Java developers think that good encapsulation means making a lot of stuff private or final. Actually what it often means is that the code is not fit for re-use, you end up re-writing code to do the same stuff that in a more open way and use that. IMHO if you are a Java developer that automatically defaults to private and final methods, forces the use of singletons or factories instead of trying to make POJO JavaBeans which can then be used as singletons (or as ordinary objects, as the need arises) then you ought to consider yourself an orthodox developer that is probably not like by anyone forced to re-use your code.

      Part of the problem is the attempt of Java library writers to try and protect the user from themselves. I used to do this but after using so many other libraries over the years I now think this is misguided. Now I try and make POJOs and POJO services whereever I can and make sure I properly Javadoc what needs to happen and also check the preconditions and arguments of all method calls. IMHO I find that in later stages of a project I have access to all sorts of information I need, rather than having to continually go back and publish formerly private methods due to inflexible and closed interfaces. A little bit of encapsulation is good (avoid non-final public members for sure) but that does not mean encapsulating yourself into a straightjacket is good either

      Sorry for getting a bit off-topic there, but I hear your pain with the currently 'orthodox' way that Google close their framework off. If there are any Java devs reading out there - keep it POJO if you can and unless you have an extremely good reason for using a private method you should make it public (which also helps unit testing too). And ffs write *meaningful* Javadoc about what can and can't cause usage of the class to fail (eg. preconditions, what argument values are invalid etc).

    23. Re:Eric Schmidt, master of non-answers by coinreturn · · Score: 2

      Anyways, fragmentation is good for the market.

      Then why are all the fandroids screaming that the market is fragmented?

    24. Re:Eric Schmidt, master of non-answers by the_B0fh · · Score: 2

      who the hell started with the "wants to consume content which requires Flash" bullshit?

      It's just "she wants to use flash" or "she wants flash to run on her tablet" or some other simpler english, pretty please!!!!!

    25. Re:Eric Schmidt, master of non-answers by Galestar · · Score: 4, Funny

      you're doing it wrong

      --
      AccountKiller
    26. Re:Eric Schmidt, master of non-answers by ILongForDarkness · · Score: 2

      I think last gen iPhone being nearly the same as the top of the line has more to do with single manufacture/single model than anything else. If you buy an iPhone you are buying a high end phone. if you continue to buy a high end Android phone you probably will get a similar experience.

      But ... there is the love/hate with the fragmentation: you might get enough of what you want from a smart phone from a cheap Android. You aren't going to get the full experience but it might be close enough for what you want. Similar to people buying low end additions of Windows. Doesn't have everything but if it has everything you want who cares? It leads to a lot of confusion though because people say just do X, oh wait no your device doesn't support that because it is the cheap version. Sorry.

    27. Re:Eric Schmidt, master of non-answers by Missing.Matter · · Score: 2

      The higher end phones have faster processors, bigger screens, better quality screens like OLED, better construction, better cameras, they're thinner etc. What I'm trying to say is that there is a certain baseline experience in Windows Phone and iOS. You don't buy a better iPhone or a better Windows Phone just to make sure that your apps run okay or that the OS isn't laggy or you're lacking a certain sensor or your touch screen is low quality. That's all assured with the base model. With Android, the cheap base models are garbage and your experience using them is similarly garbage.

    28. Re:Eric Schmidt, master of non-answers by wzinc · · Score: 3, Informative

      Nope, it's free for iTMS purchases and $25/yr for all else. I've never been anywhere AT&T didn't have a good signal, or I can just hit the cache button if I'm going on a plane. As for the EULA, never happened and couldn't care less. I don't do illegal music, so I have nothing to hide. The only reason Apple would change anything in a negative way is if the music industry forced them, such the old limits to five devices or ten burns of a playlist. Apple has been fighting for the consumer for a long time.

    29. Re:Eric Schmidt, master of non-answers by packslash · · Score: 2

      fragmentation isn't a marketing term for about 10 million samsung galaxy S owners. "it's amazing to me that in the Android world you can buy a brand new Android phone with an OS 2 versions out of date, and that phone will never be upgraded. THAT is a problem. not talking about 4 year old phones not getting the latest release. We're talking about brand new phones that are out of date, out of the box. This isn't a fairy tale." Sounds like a marketing term to me!

    30. Re:Eric Schmidt, master of non-answers by Daniel+Phillips · · Score: 2

      Openness and Google and other geek-factors don't enter into it.

      On your planet, maybe. On my planet, every single person on the street knows Google, uses it, and generally respects it as a brand. And while openness may not be the first thing they think of when they get a phone, it quickly jumps in priority as soon as words like "how would you ever know if your phone is spying on you?" enter the conversation or "you can get so much more free stuff". Free? Deal.

      --
      Have you got your LWN subscription yet?
    31. Re:Eric Schmidt, master of non-answers by jo_ham · · Score: 3, Insightful

      And I have a few that went the other way - they had Android and decided they didn't like it and went to iPhone. One of them was a high-spec Android owner, the other had a crappy Android phone. One moved because he preferred iOS, the other (with the crappy handset) really doesn't like Apple but the device he had was beyond frustrating so he got a 4S.

      I asked him why he didn't go for a Galaxy S II or similar and he said he was just fed up with how bad the experience was.

      I also know people who bought Galaxy S's (esses?!) and love them.

      I don't think it's necessary to be geeky to appreciate Android phones, but it certainly doesn't hurt given what I've seen while using them (and I've tried a whole gamut from really poor to really good).

    32. Re:Eric Schmidt, master of non-answers by BitZtream · · Score: 2, Insightful

      People didn't talk about desktop fragmentation in the PC era, people don't talk about console fragmentation when you need specialized controllers to interact with many of today's games.

      Uhm, before XP, when there were new versions of Windows every year or so (if you count OEM updates), fragmentation was a topic of discussion.

      Linux fragmentation is the #1 or #2 reason companies won't bother with supporting it

      Most Android devices struggle to be close enough to iOS to draw in people looking for iOS devices, thats not innovation.

      iOS is being updated fairly often with new features wanted by developers and users on a fairly constant basis, how is that stagnation?

      You need to stop talking in 'theoretically this is whats going to happen' and come back down to 'whats actually going on right now' because they are two entirely different things.

      As for your take on the 'winning' thing, I think you're getting fed incorrect data at this point, considering the same could be said about Apple's iPhone in 2007-2008 ... you know, when Google bought Android so they could copy Apple ... after they said it was silly?

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    33. Re:Eric Schmidt, master of non-answers by jo_ham · · Score: 4, Insightful

      Nonetheless, "fragmentation" is a marketing term being bandied about by Apple apologists.

      That's a dangerous assertion to make, and smacks of putting your fingers in your ears and saying "la la not listening".

      Android has some absolutely stellar features and plus points but it also has downsides, and to just attempt to "shush" them by claiming it's just Apple apologists does nothing to help Android.

      Fragmentation is a problem, and one created by one of the major benefits of Android - the wider selection of hardware that it will run on. iOS minimised the problem by limited the number of devices that developers need to target and test against, which gives you the benefit that apps in the store really only need a couple of branches: iPhone or iPad > Pick one of a few options regarding model. It has the downside of limited model selection compared to Android.

      Don't get me wrong, I think Android is in the ascendency and everyone is the better for it (including iOS users), but ignoring constructive criticism is not a sensible way to go about things.

      Your wife is also going to be disappointed with whatever tablet she gets if she wants to watch flash content, since Adobe pulled the plug on it.

    34. Re:Eric Schmidt, master of non-answers by packslash · · Score: 2

      your theory falls down when one realizes that winphone7 was so late to market. If windows phone 7 came out in 2008 it would be doing a lot better with the "general Public" Marketing has very little to do with the iPhone's and IOS's lasting success. Also using your salesman incentive argument win phone 7 should be doing better as ms actually pays.

    35. Re:Eric Schmidt, master of non-answers by neokushan · · Score: 5, Insightful

      That's a problem with Android - there are a LOT of sub-par devices out there and people that start off at the low-end are often left with a bitter taste. At least with iOS, the devices are reasonably capable, even the older models. I dare say that the experience your friend with the crappy device had would have been much improved just by moving to a higher-specced android phone, but the important thing is that they're happy.

      I'm going to be honest - I'm a big Android fan, but I am a geek through and through. I rooted my phone within a week of getting it and installed a custom ROM the next day - that alone was tonnes of fun for me and a plus to the Android experience. However, when family and friends ask which phone they should get, I'll never say "Get Android, it's da bomb!" partly because I know the reasons I like Android are reasons they'll hate it and also because I don't want yet another device to support. However, I will recommend devices that meet their needs and there's almost always an Android that fits in there, but I'll always say "Go into a store and play with it, ONLY get it if you like it". If anyone buys a phone just because its cheap or because people rave about it, yet end up not liking it, it's really their own fault for not trying before buying.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    36. Re:Eric Schmidt, master of non-answers by edmicman · · Score: 4, Informative

      Pretty much any Google app is better on Android. The way I've viewed it, when recommending phones to people, is that it depends on which non-phone camp you're in. I don't use iTunes, my email is Gmail, news reader is Google News, etc. My music is mostly from Amazon and stored in a folder structure but any major player is able to read the tags. And I've been dabbling in Google Music lately anyway. So Android gives me the best Google experience. The Google+ app is always going to get Android updates and features first, as is most any other app by Google. And like you mentioned, Google maps navigation is top notch. However, if someone has their life in iTunes and would love to have that seamlessly carry over to their phone. I'll tell them they might prefer the iPhone. For what it's worth, my wife just upgraded from a BB Storm 2 to an iPhone 4S. It was hardly a seamless upgrade and she spent the first few days complaining about how much of a pain it was to set up the new phone and make it do what she wanted. She even said at one point that it was easier to set up the BB than the iPhone! Ultimately I don't think there's that much of a difference anymore either. Both are a phone with a button and a bunch of app icons. Both get you on the web. Both have Facebook. However I've yet to still see anything really that the iPhone does better than my Galaxy Nexus.

    37. Re:Eric Schmidt, master of non-answers by Missing.Matter · · Score: 2

      Good for you. But that's not what you said. You said: "Phone storage doesn't matter." What you really meant was "For me, because I'm granfathered into an unlimited data plan or I'm lucky enough to be on a carrier with unlimited data, phone storage doesn't matter. Sucks for you losers." For the rest of us, yes, it does in fact matter.

    38. Re:Eric Schmidt, master of non-answers by pscottdv · · Score: 2

      Only on price though. Android runs terribly on low end smartphones

      I don't know about that. I have a Samsung Dart, which is pretty low-end, and it works fine with Android 2.3. I like it because it is small, thin, and inexpensive ($130 with no contract). It does not run everything. Flash player, for example, is not available from the Android market for this phone, presumably because it is not powerful enough to run it. I don't mind, I have other toys for watching video.

      My brother-in-law has a much more sophisticated Android phone that "does everything" including 3D video and 4G. It also has an enormous form-factor and price, both similar to the iPhone.

      I guess you could say that this is fragmentation, but to me it feels like consumer choice.

      --

      this signature has been removed due to a DMCA takedown notice

    39. Re:Eric Schmidt, master of non-answers by forkfail · · Score: 2

      Naw, it's more the regularity of the posts, the stock phrases and corporate memes, the timing (seconds after an article appears on the front page, but with perfect grammar, spelling and accurate links), the limited number of accounts that do this, but do it every. single. time.

      --
      Check your premises.
    40. Re:Eric Schmidt, master of non-answers by tknd · · Score: 2, Insightful

      However, in the Android world you can buy a brand new Android phone with an OS 2 versions out of date, and that phone will never be upgraded. THAT is the problem.

      Oh, I see the name of this game now. Let's change "fragmentation" to mean whatever we want it to mean.

      First it was the fact that different devices existed though they were generally running the same Android version. Everyone complained "oh, fragmentation." Jobs and company went out and told the world you can't build a high quality product if you don't control the entire market vertically. That was fragmentation.

      Of course many developers came out and said it wasn't really a problem. You simply target a lower API level and develop from that. If you're using undocumented features and digging in beyond what was specified, that was your problem. That's like tweaking your car's engine beyond specification with something like a turbo charger and later calling up the manufacturer and asking why the engine blew up because you used forced induction.

      Nevermind that iOS has similar fragmentation issues. The screen on an iphone 3gs is not the same resolution as an iphone 4 which is not the same as an ipad. Fragmentation?

      Now you say, "OMG, you can buy a phone with an old version of android!" Well no shit. The idea wasn't to pigeon hole everyone into something. That's Apple's business model, the model of complete control. When Apple decides "hey, buy a new phone" they can and will force people to do it and nobody dares to stand up to them.

      For example let's talk about Siri. Siri is perfectly capable of running on EXISTING iphone 4 devices. It was shown to be possible by some hackers. Hell, Siri itself was running on iphone 3gs when Siri was an independent company. Then Apple came in and bought Siri, dropped the Siri app from the app store, and re-released it as part of iOS 5 and RESTRICTED it to iphone 4s. How is that not fragmentation? How is that not FORCED product obsolescence?

      Oh yeah, that's right. Jobs and his legacy is your savior. We must justify every decision even if it potentially hurts us. But if someone else does it? EVIL! HATE! ALERT THE BLOGOSPHERE! F-R-A-G-M-E-N-T-A-T-I-O-N!!!

    41. Re:Eric Schmidt, master of non-answers by blackraven14250 · · Score: 2

      A few Android apps don't have quite the polish of the iOS versions, but I can say that most of the issues surrounding the slow loading of apps and choppy graphics can be fixed by installing a ROM that doesn't contain the bloatware that comes standard on most phones. It's disgusting how much crap comes on the phones, and basically renders them a piece of shit when they're damn good in a configuration closer to what Google intended than what the carrier wants to push onto the end user.

      A key exception to this is the Nexus line, which aren't allowed to have any bloatware AFAIK due to contractual reasons. Google intends them as developer phones, so they want them to be as vanilla of an Android experience as possible.

    42. Re:Eric Schmidt, master of non-answers by Sancho · · Score: 4, Informative

      I'm not the AC to whom you replied, but I did the same thing s/he did. Had an iPhone, switched to Android, and switched to a 4s as soon as my contract was up.

      The reasons for moving to Android were openness and ability to side-load. It turned out, these weren't that big a deal.

      First of all, ideologically, Android isn't really open for me. It's open in the same way that Tivo is open. Parts are based on Linux, other parts are new. Some of it is available to me, some of it isn't. But what matters (to me) is that I can't just download the source, compile it, and end up with a working build. At BEST, with a lot of work, I can get something on my phone which resembles the original (minus e.g. Google's apps, which are half of the reason to get an Android phone to begin with.) At worst, the phone has a locked bootloader, and you can't put a new ROM on there.
      If my two choices are both effectively closed, then the openness of the platform is irrelevant.

      I also found that I never cared to sideload. It wasn't difficult to do--I just never had a reason to. And all of the apps I had on my phone would have gone through the Apple App Store approval process--I wasn't doing anything really off the wall. So I had no need to sideload.

      Then there's the issue of upgradeability. I figure that my Android phone would have been vulnerable to known exploits for about 1/4 of the contract. That's due to the carrier/manufacturer failing to update in a timely manner. The build process is fairly onerous, so I wasn't going to do it myself. Going with Cyanogen, I got updates faster. But I don't want to have to do that. Apple updates very old hardware to new OSs. Their time-to-fix vulnerabilities isn't much (if any) worse than Cyanogen.

      So at the end of the day, I had to decide based on features. Both Android and iOS do what I want them to, but iOS does it cleaner and smoother.

    43. Re:Eric Schmidt, master of non-answers by Americano · · Score: 2

      No, they didn't complain about fragmentation per-se in the Windows market, because regardless of the machine you bought, it ran pretty much the same software, and looked and behaved the same. But remember all the flak Microsoft took for it's multitude of slightly-different editions of Windows? Remember all the grousing about bloatware and crapware added by manufacturers?

      That's what you're seeing with Android: it's got a bunch of slightly different editions, not all hardware supports all editions, and it almost ALWAYS comes preloaded with bloatware. Android's "run-anywhere" openness is double-edged: the experience is uneven & unpredictable - it means very little to say "powered by Android," because that same phrase could be used to describe a $10 piece of plastic junk, or the latest and greatest device rolling out of Samsung's high-end design lab. "Powered by Android" means - what, exactly - in those two cases? The experience, the reliability, even the basic interface are going to be incredibly different. And this is the real "fragmentation" danger.

      Your critique of technology monoculture only has teeth if iOS is the OS powering a huge portion of all these devices, to the extent that there is no real legitimate alternative. Android, the Blackberry OS, WP7, WebOS, Symbian, and Nokia's various OS experiments would all like a word with you about your claims of a monoculture in smartphone OS. You might as well complain about Toyota's creation of a stagnant "monoculture" because they're the only company producing a midsized sedan named "Camry". Other quite comparable midsized sedans exist on the market; That Toyota doesn't offer 12 models of Camry doesn't mean they've created a monoculture.

    44. Re:Eric Schmidt, master of non-answers by na1led · · Score: 2

      iOS may have more polished apps, but it lacks a lot of good apps only available for Android. I haven't seen any good Emulators available for iOS, I have PSXE, SNES, NES, Amiga, and many more. But that's what you get with an OpenSource platform.

      --
      -- By all means let's be open-minded, but not so open-minded that our brains drop out.
    45. Re:Eric Schmidt, master of non-answers by Knuckles · · Score: 3, Insightful

      You don't? Merriam-Webster sees it differently:

      Definition of CONSUME
      transitive verb
      1: to do away with completely : destroy (fire consumed several buildings)
      2 a: to spend wastefully : squander
      2 b: use up (writing consumed much of his time)
      3 a: to eat or drink especially in great quantity (consumed several bags of pretzels)
      3 b: to enjoy avidly : devour (mysteries, which she consumes for fun — E. R. Lipson)
      4: to engage fully : engross (consumed with curiosity)
      5: to utilize as a customer (consume goods and services)

      intransitive verb
      1: to waste or burn away: perish
      2: to utilize economic goods

      But be that as it may, the original complainer didn't seem to be annoyed by the term "consumed", but by the "content which requires flash" construction; else his alternative suggestions would probably have been along the lines of "wants to watch content which requires Flash".

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    46. Re:Eric Schmidt, master of non-answers by Coolhand2120 · · Score: 2

      Better to keep your mouth shut and be thought a fool than to open it and remove all doubt.
      -Mark Twain

    47. Re:Eric Schmidt, master of non-answers by Algae_94 · · Score: 2

      Not to get too off topic, but when was the last time you went to McDonalds? It isn't considered awful food by millions and millions of people (or whatever their signs say now). Why would people eat it if it was awful? It's not like it's half the price of other places. They also do have some food choices that aren't bad for you. nutrion info at McD's.

    48. Re:Eric Schmidt, master of non-answers by Goaway · · Score: 2

      You can make quite a bit of money from an underserved market even if it is small.

      But if the effort is too big, or you have to limit yourself to a subset of an already tiny market, your profit is going to evaporate pretty quickly.

    49. Re:Eric Schmidt, master of non-answers by shutdown+-p+now · · Score: 2

      unless you have an extremely good reason for using a private method you should make it public (which also helps unit testing too). And ffs write *meaningful* Javadoc about what can and can't cause usage of the class to fail (eg. preconditions, what argument values are invalid etc).

      The second part of this is precisely the first part cannot always be done. If you make a method public, it becomes a part of your contract - you have to document it, do full argument validation (because who knows what will be passed to it by third party code?), and you'll have to keep it around in future versions of your API for backwards compatibility.

      Making things public is not free. In fact, it can be very expensive, depending on your back-compat requirements. Consequently, if you're making a public platform or framework, the only sane design choice is to only make things public when you fully understand the implications of doing that for every particular class and member, and otherwise default to private.

    50. Re:Eric Schmidt, master of non-answers by Sancho · · Score: 2, Informative

      First it was the fact that different devices existed though they were generally running the same Android version. Everyone complained "oh, fragmentation." Jobs and company went out and told the world you can't build a high quality product if you don't control the entire market vertically. That was fragmentation.

      I never heard that definition, so I can't really speak to that. I'll say that it doesn't make any damned sense, unless hardware vastly differed. Then you're having to optimize to particular amounts of RAM or processor speeds. The iPhone has had this particular issue ever since the 3G was released, of course.

      Of course many developers came out and said it wasn't really a problem. You simply target a lower API level and develop from that.

      Weellll, yes, but that's part of the fragmentation. There's the nice, shiny, easy-to-use APIs, but you can't use them if you want to target all devices. That right there is the definitive fragmentation that most people mean when they use the word.

      Nevermind that iOS has similar fragmentation issues. The screen on an iphone 3gs is not the same resolution as an iphone 4 which is not the same as an ipad. Fragmentation?

      Most people, when referring to Android fragmentation, are referring to phones. Tablets didn't even run the same OS until very recently (except for a few that ran older OS.)

      Apple segmented their app store into iPad and iPhone sections, and while you can run the phone apps on the tablet, it's clearly not the optimal use.

      As for the 3gs vs the 4's resolution, it's an even multiple, which means that the phone can use scaling to abstract 99% of problems away.

      Now you say, "OMG, you can buy a phone with an old version of android!" Well no shit. The idea wasn't to pigeon hole everyone into something.

      Yup. Android lets you buy a new phone with existing, in-the-wild exploits. Awesome!

      But the point of the whole discussion is fragmentation, and lots of different OS versions is just that. Either devs write for the older OS or they leave it behind.

      For example let's talk about Siri. Siri is perfectly capable of running on EXISTING iphone 4 devices. It was shown to be possible by some hackers. Hell, Siri itself was running on iphone 3gs when Siri was an independent company. Then Apple came in and bought Siri, dropped the Siri app from the app store, and re-released it as part of iOS 5 and RESTRICTED it to iphone 4s. How is that not fragmentation? How is that not FORCED product obsolescence?

      If an APIs existed which took advantage of Siri, that would be the fragmentation that everyone talks about.

    51. Re:Eric Schmidt, master of non-answers by hitmark · · Score: 2

      I think the problem is that what one article means with fragmentation is not the same as another article.

      Quite a few see the various Sense, Blur and Touchwiz interfaces as fragmentation.

      Others see the variation in Android versions as fragmentation.

      And the last bunch see the actual variation in formfactors and hardware internals as a fragmentation.

      The first kind can be a problem for those that try to make app interfaces that blend in with the phones existing interface.

      The second will be a issue for all those that want to make use of the latest nifty APIs.

      The third becomes a issue if one try to optimize for performance, especially games and similar, via the NDK, or do not properly leverage the UI scaling tools built into Android.

      But Google seem to be addressing all of these in various ways.

      Recently they added a requirement for the 4.x theme to be present at all times (why this was not there from day one boggles the mind). And when they introduced the Fragments UI system they provided a lib that allowed such UIs to work on pre-Fragments version of Android (as far back as 1.6, iirc).

      The NDK angle may be the most troublesome in the long run.

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    52. Re:Eric Schmidt, master of non-answers by scot4875 · · Score: 2

      Yeah, and if we try to do anything about it it's socialism.

      --Jeremy

      --
      Jesus was a liberal
    53. Re:Eric Schmidt, master of non-answers by quacking+duck · · Score: 2

      I tip my hat to you (and other following posts with a similar mindset), for giving advice logically, based on the user's needs and not your platform preference.

      I'm a Mac user since the early 90s. I obviously prefer it and believe that on the whole OSX is better for general users. Whenever someone asks for buying advice, I am upfront with this, but based on their wants and needs (especially budget) I have no qualms saying a Mac might not be for them.

    54. Re:Eric Schmidt, master of non-answers by SplashMyBandit · · Score: 4, Insightful

      If you are not documenting and validating the input methods of your methods (regardless of whether they are public or private) then you are making a colossal mistake. How do you know when the maintainer who comes after you is going to refactor the class; answer: you don't. If you are not validating your inputs and thinking out the overall object state when you first write the method just because you're too lazy to then no wonder people like myself are forced to re-invent the code people like you write. I *hate* re-implementing code that other people have done, but it turns out that people that don't design for re-use by others (that is, hide methods that are required to extend functionality while maintaining invariant conditions) are the majority and mistake the contrived examples given in textbooks (showing you how to hide *critical* methods) as examples take this as what should be done for *all* classes.

      You are welcome to think I'm full of it. Like I said, I used to think as you do, but with a lot more experience of using other's code I realized how unfriendly this is for third-party devs trying to use your code (who will need to re-use it in ways you never thought of - thanks to their particular requirements). For example, just try extending JavaMail to allow to arbitrarily muck around with MIME mail parts and nest them as you see fit. Turns out the methods you need to do that are all implemented but hidden away, yet looking at the source (thank goodness I had access to it - not always the case) there was no good reason for hiding it away that I could see, apart from it being 'orthodoxy' (which means the author never thought about it too hard, as they probably never had to try using his own code while trying not to access the source, as a user would try to do). In the end I had to wastefully re-write a chunk of Javamail for the clients use. This kind of crap is why 'Not Invented Here' is so prevalent - because orthodox Java development as promoted by the textbooks and circuit speakers goes too far so as to make encapsulation a straightjacket. Some encapsulation is good, but too much is worse than too little, if you know what you are doing (as most professional Java devs do these days - which is why it is so frustrating). Basically I see the excessive hiding of information as an unhelpful 'denial of service' by the author - maybe because they are too damned lazy to document the method, validate its inputs, or test it in isolation (of course getter/setters [accessors/mutators] don't need this level of work), and it sucks when I have to re-implement what they did just because they unnecessarily closed off a few very helpful methods. I'd bet you money that if you've been developing for a while you've had this yourself. One last thing, when developing a class I believe you should always be thinking of how the class could be used in a stand-alone fashion (as any Java Bean can be) without the rest of the machinery of your particular application. The corollary is that the smaller the dependencies (example, choose JRE standard classes like java.util.logging over third party libraries) the easier it is for other people to use. Most Java developers don't try to minimize their library dependencies and think whether each library contributes enough to justify the extra weight, but they should. This is why some small Java programs come with hundreds of extra JAR libraries, some of which have very tenuous utility for the application (and sometimes a single class is used from a library, which brings in a raft of other libraries, when a simple implementation of the simple class would have saved the dependency mire).

      I understand what you are saying. I just happen to disagree that methods should be hidden by default. With proper documentation and unit test examples for client developers to follow (you do unit test, don't you?) then trying to 'protect the developer from themselves by hiding functionality' becomes unnecessary - which gives the client more freedom to use more of your classes, and therefore the client

    55. Re:Eric Schmidt, master of non-answers by dudpixel · · Score: 2

      I dunno, once upon a time the iPhone WAS the market (I really dont see blackberry as a competitor to the iphone), so Android has convinced at least 50% of people who may otherwise have bought an iphone (in the absence of any other choice) to buy an android phone.
      Some of those will switch back to iphone, or will choose iphone next because they disliked some of it...

      but the fact is that android hasn't failed, and is still competing quite well in the market despite any fragmentation or whatever people want to call it.

      People love to talk in absolutes, like there can be only 1 winner and that everyone should use the same phone. People think something is either the best or it is crap...

      but in the real world we just find 2 very successful platforms, with a bunch of vocal users who support each one.

      the media loves the OS wars though, and here we are feeding the trolls...

      I've owned 2 android phones, and never felt any impact of this fragmentation.

      If a device manufacturer screws up, and makes a device that doesn't work well with android, is that really the fault of android?

      I accept that developers have to do a bit more work to cater for more devices, but its no different to what we've had with windows for years.

      so yeah, fragmentation exists, but for your average android user, its not that big a deal. maybe you might find an app that doesn't work well on your phone. its rare, but if it does happen, just look for another app...

      --
      This seemed like a reasonable sig at the time.
    56. Re:Eric Schmidt, master of non-answers by Americano · · Score: 2

      ... then the term "monoculture" is meaningless as he's used it, and represents neither insightful commentary, nor incisive criticism. "All iOS devices run iOS, therefore it's a monoculture" is a reflexive redefinition of the term, apparently in an attempt to sound smart and "science-y". The current situation in the phone market is, in fact, the very opposite of a monoculture - it is a healthy, diverse ecosystem with many competing systems available, across a range of hardware. If something happened to instantaneously destroy or compromise every Apple device on this planet, the vast majority of mobile devices would continue working just fine.

      The fact that Android runs on a huge variety of devices *isn't* seen as the problem; the fact that Android runs - OFTEN POORLY - on many of those devices is. Android runs the risk of developing a "caveat emptor" reputation: The carriers are crippling the devices with bloatware and lockdowns; They are cramming the system into cheap, effectively disposable phones which are underpowered; and they are providing virtually zero longer-term support for OS upgrades beyond the bare minimum that they might be required to do to keep your phone marginally operational.

      This unevenness in user experience is what is going to hurt Android in the long run, and make the "Android" brand irrelevant as a selling point, because "powered by Android" will describe everything from the cheapest POS on the market to the most expensive, best-designed Samsung/Motorola/HTC/etc devices. It won't be a competitive differntiator versus other devices, it'll be something that consumers say, "Yeah, and... does this Android model work Last Android I had was a piece of shit." in response to.

    57. Re:Eric Schmidt, master of non-answers by neokushan · · Score: 2

      Hi there,

      My name is neoKushan, but today I'll be standing in for reading comprehension.
      Words come in all shapes and sizes, but what's magical about them is that their meaning can change depending on the context.

      What is this magical "context" thing? Well, to put it simply, context is the other words that are near and around the words and phrases we're looking at. You can't read a sentence by just picking out a few choice words, you need to read all of the surrounding words to really understand what it means. For example, in the above instance you managed to pick out the phrase "Get Android, it's da Bomb!" and rolled off in a tirade of idiocy, however you failed to notice that the preceding 3 words were "I'll", "never" and "say". This is both a great example of context and an even better example of failing at reading comprehension.

      Luckily, all is not lost! Many local authorities provide night schools and classes for those who have trouble with reading comprehension. Please, contact your local educational establishment and ask them about their night schools on basic reading and writing skills. In a matter of weeks, you too could be adept at reading simple words and phrases that are surrounded by other simple words and phrases. People will respect you more and you'll be able to interact properly on the internet, a wonderful place full of words, phrases and lots and lots of contexts. Don't delay, sign up for education today!

      Thank you for your time.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
  2. Just playing with words by SharkLaser · · Score: 3, Insightful

    The difference, as he explains it, is that differentiation means manufacturers have a choice, they're going to compete on their view of innovation, and try to convince consumers that their innovation is better than somebody elses whereas fragmentation is quite the opposite.

    How is that different, and how is fragmentation quite the opposite? It's not. Fragmentation on Android is real problem. Of course Eric Schmidt is going to say it's not a problem, or that it doesn't even exist. Companies always deny problems. It's not a bug, it's a feature!

    1. Re:Just playing with words by jedidiah · · Score: 3, Insightful

      What's a problem exactly? How is that different than any other platform that has diverse hardware and different OS release levels applied to it?

      It makes for some sensational rhetoric but seems to be less meaningful in practice.

      I can't play the latest and greatest CPU/GPU crushing game on an ION but no one seems to think that's such a great tragedy.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:Just playing with words by Troed · · Score: 5, Insightful

      Well, the wordplay is correct. You could also say that the mobile market is fragmented between iOS and Android, yet we call that differentiation and innovation.

      After all - we could create a government mandate that all computers have to be x86 based - that would've stopped a lot of fragmentation. Would it have created a better world?

    3. Re:Just playing with words by hedwards · · Score: 3, Interesting

      Except that Google provides developers with tools for managing that and I'm sure that there's a list of safe features to use as well. The typical people making a big deal out of fragmentation are Apple Fanbois that can't imagine how an OS could exist where all devices aren't identical.

      I haven't personally found that I wanted to use an App that wasn't available for my particular handset but was for other Android handsets. I doubt very much that I'm alone, at least when it comes to folks that waited until the market got really going good.

    4. Re:Just playing with words by Missing.Matter · · Score: 3, Insightful

      It might not be different, but it is a bad thing and consumers do suffer. Consumers go into a cellphone store and they buy an android phone, thinking they're buying into a certain level of quality or experience. But Android runs on some pretty craptacular phones and tablets these days. It's a complete crap shoot as to what kind of specifications and capabilities any given android phone has. Contrast this with the iPhone. As a consumer you know exactly what you're getting even if it's a last gen phone. Contrast this with Windows Phone. Even if you buy the lowest end windows phone or a last gen phone, it's going to have the same exact capabilities as the top of the line.

    5. Re:Just playing with words by Belial6 · · Score: 2

      Agreed. And for a product line that has so few models, I am amazed at the level of incompatibility that exists on the iOS line of products.

    6. Re:Just playing with words by Galestar · · Score: 2

      You've missed the point. You either have a reading comprehension problem, or you are just plain dumb.

      --
      AccountKiller
  3. Member of Executive Team... by jkyrlach · · Score: 4, Funny

    put's positive spin on a potentially negative product quality. Film at 11.

  4. Shocked by Overly+Critical+Guy · · Score: 4, Funny

    Totally shocked that the CEO of the company that licenses Android insists that it's not fragmented. Could we also get China's opinion on internet censorship or Rush Limbaugh's thoughts on Obama?

    --
    "Sufferin' succotash."
    1. Re:Shocked by symbolset · · Score: 3, Funny

      His role used to be "world's most expensive babysitter" but the kids had already grown up.

      --
      Help stamp out iliturcy.
  5. Eric Schmidt: the New Google Information Minister by mveloso · · Score: 3, Insightful

    In the footsteps of Iraqi Information Minister Muhammed Saeed al-Sahaf comes Eric Schmidt:

    "No, what you are seeing is not fragmentation, it's differentiation!"
    "Google search plus your World is not favoring Google+ results - it's just reranking them more appropriately!"

  6. Re:Android apps by danbob999 · · Score: 2

    I never had a virus nor ever met anyone who had a virus on its mobile phone.
    These companies are just trying to profit from uneducated users.

  7. Android reduces fragmentation by danbob999 · · Score: 3, Interesting

    As I said in a previous discussion, Android reduces fragmentation.

    The main fragmentation that interest developers is the one between platforms, not within a platform. If Apple and RIM both switched to Android, it would be much easier to develop for mobile devices. They add a lot of fragmentation by continuing to push their proprietary platform. Google actually removes fragmentation by giving away for free an OS that anyone can use. There would be much more fragmentation in the mobile world if HTC, Motorola, Sony, Samsung and LG all pushed their own OS like Apple and RIM are doing.

  8. Re:I might be missing something but.... by leftover · · Score: 2

    Verizon, Sprint, et. al. are most certainly NOT paying anything for your phone. They are merely fronting the money. You, the users, are paying it all back with more than enough profit.

    What this arrangement does, however, is to make the phone companies Google's immediate customers. Users are somewhere in the background, with no voice at the deal-cutting table.

    --
    Bent, folded, spindled, and mutilated.
  9. Manufacturers lying about ICS by kmahan · · Score: 2

    How about calling the manufacturers LIARS. They committed to putting ICS on handsets and now are going back and saying "just kidding."

    In my case the Moto Droid 3. Bought it after hearing Moto commit to putting ICS on their new handsets. Now they won't even talk about ICS and the Droid 3. Luckily Cyanogen has stepped up.

    --
    Invalid Checksum. Retrying.
  10. fragmentation not a problem by khipu · · Score: 5, Interesting

    Most apps work fine across all common Android versions; the only ones that don't are those that require functionality that just wasn't available on earlier devices. Most of the so-called "fragmentation" is things like manufacturer-specific apps and launchers. Those do exactly what Google says they do: they allow manufacturers to differentiate themselves from one another. That may not be a good thing (I prefer "pure" Android), but it isn't a problem.

    I think a lot of the complaints from developers about fragmentation is complaints from iOS developers, who are used to an unusually rigid level of constraints across devices and have developed bad coding practices (like hard-coding coordinates and layouts etc.) because of it.

    1. Re:fragmentation not a problem by LordLucless · · Score: 2

      That may not be a good thing (I prefer "pure" Android), but it isn't a problem.

      And the thing is, if you prefer "pure" Android (like you, and like me) Google produces an official reference phone in the Nexus line.

      I understand there's issues in the US, where apparently certain handsets aren't allowed on certain telco networks, but that's really a problem with your telcos than with Android - why they are allowed to discriminate based on handset instead of simply on features is beyond me.

      --
      Just because you're paranoid doesn't mean there isn't an invisible demon about to eat your face
  11. Marketing by Anonymous Coward · · Score: 3, Insightful

    If you are afflicted with bad press, argue the semantics.

    Since it's technical stuff, nobody but the geeks are going to understand, and nobody listens to the geeks.

  12. It's not the apps, it's the OS by Superken7 · · Score: 5, Insightful

    Most apps run well on every android version thanks to the design of API cross-compatibility (I have experienced this myself, being an early android developer).

    However, I don't think you can avoid the fact that the OS itself is fragmented when your OS takes 6 months to a full year to be available on the majority of android handsets.

    In addition, has Mr. Schmid had a look at this chart, put up by google themselves?
    http://developer.android.com/resources/dashboard/platform-versions.html
    It reads OS fragmentation all over it! And this is PRECISELY what pisses many (geek) users off, that they can't get the latest and greatest or that new phones come to market being outdated!

    1. Re:It's not the apps, it's the OS by brainzach · · Score: 3, Interesting

      Windows machines are heavily fragmented between Windows 7 XP and Vista. It will just get worst when Windows 8 comes out.

      The problem isn't fragmentation. It is the lack of OS updates.

    2. Re:It's not the apps, it's the OS by SoftwareArtist · · Score: 2

      Exactly. As a developer, I've had very little problem with differences between devices. Sure there's a lot of variation in terms of screen resolutions and such, but the OS provides tools to deal with that. And the custom skins different vendors put on the UI really don't impact me much at all.

      But it's really irritating that I still can't require anything later than Android 2.2 without excluding a large part of the potential market (and even at that I'm losing about 10% that are on 2.1 or earlier). The various companies involved really need to get their act together. They should commit to keeping all devices up to date for a reasonable period (at least a year) after they're sold, and to releasing those updates in a timely manner.

      --
      "I'm too busy to research this and form an educated opinion, but I do have time to tell everyone my uninformed opinion."
  13. Re:I might be missing something but.... by brainzach · · Score: 2

    I know people who prefer the Sense skin over stock Android.

    There are flaws with the stock versions of Android when it comes to ease of use. It is nice if you want customizations and freedom, but they don't always provide the best experience to the average user.

  14. Different can be good. by erick99 · · Score: 2

    I am okay with a little fragmentation if it means lots of choices in phones. Shopping for smartphones, for me, is like being in a big candy shop and trying really hard to choose. And, while I understand how appealing the iPhone is for so many, I really like having lots of choices (I chose and really love my HTC EVO). The iPhone is a great choice for many but many others like other choices. Too much "sameness" doesn't feel good to me though it feels great to others. I don't think either camp is right or wrong - just another choice to make.

    --
    http://www.busyweather.com/
  15. Re:Fragmentation=Doom by Fahrvergnuugen · · Score: 4, Insightful

    This is the mother of all failed analogies. All of the devices you mentioned are interoperable and standardized in very important ways. Why do you think all Ryobi batteries are interchangeable? Why do you think all cars have the same basic layout and conform to the laws of the land? Why do all tv sets have the same basic standardized ports and display the same basic standardized signal? Why does just about any thermostat work with just about any furnace?

    As an iOS developer, Apple has made it really easy for me to write code once and I know I only have to test it on about 3 devices. From there I know my addressable market is hundreds of millions of devices.

    As a consumer I have confidence that when I buy a new iPhone in 2 years, all the apps I pay for today will work in the future. I don't hesitate about making the investment because I know it can be long term. And I don't have to go setup my phone from scratch either.

    --
    Kiteboarding Gear Mention slashdot and get 10% off!
  16. Re:App examples? by gl4ss · · Score: 2

    well, make a html5 application with hardcoded coordinates.
    and then complain when it doesn't look like it should on different devices, with different sized screens, some with kb some with trackball.

    that's android fragmentation for you.

    and only an idiot would release an ics-only app right now - unless it depends on some ICS specific api.

    if you go with 2.2 things will work from friggin ziio's to fire's to samsungs to motos to lg's to sony-e's. perhaps even on that motos android watch.

    --
    world was created 5 seconds before this post as it is.
  17. Re:Eric Schmidt: the New Google Information Minist by LordLucless · · Score: 2

    Or, you know, the fact that Twitter is trying to /charge/ them for the right to index those results, and they don't want to pay.

    --
    Just because you're paranoid doesn't mean there isn't an invisible demon about to eat your face
  18. What?! Car analogies never fail... by bartoku · · Score: 2

    Why do you think all cars have the same basic layout and conform to the laws of the land?

    With cars we have compact, suvs, pick-ups, 18 wheelers...They all conform to certain standards and perform the same basic function: transporting something from one place to another along the same road.

    Android handsets represent a diverse array of cars, we have cheap compact Android handsets, we have sporty do it all handsets, we have handsets with physical keyboards fit for a certain utility, and we have the Samsung Note two-handset. But they all conform to certain standards, Android APIs and gsm/cdma/wifi/bluetooth...

    Now app developers are like tire, radio, seat cover, rear-view dice makers for cars. With the iPhone like car you know that every seat in the car is the same, the rear-view mirror is always the same, the radio slot is the same, and the tire nuts are in the same place for the three models out there. The three models are extremely popular with about 30% market share, but they are limited in how much you can customize them and still sell them on the special super ad promoted iPhone car market vs the underground jailbroken one. It is understandably easier for developers to hit that 30% of the market than the Android market.

    Now with the Android cars, a pair of dice may fit on the rear-view mirror, but they may not always look the best in certain models. There may be a standard radio slot, but not every Android car adopts that standard requiring a little extra work to get that radio installed, and some Android cars allow for giant monster wheels.

    You may want a car that will just get the job done, do just about everything well, and you do not have to worry much about it, so you grab an iPhone car. Yeah maybe you can get some lumber home from the hardware store in the iPhone car which is sedan like, but an Android pick-up truck is much more suited for the task with someone who is hauling lumber everyday. Or perhaps you are tired of paying extra to be able to tow something behind your iPhone car, so you jailbreak it, or you get an Android car that natively allows you to tether things behind it.


    The real problem are the toll booth operators of the cell phone world. It would be like if you could only use your iPhone car on the roads owned by the toll booth operator who sold it to you. Now the four major operators have roads just about everywhere, but some roads are worse than other, fewer lanes, pot holes, and some times there is only one good toll booth operator in the area you primarily drive and you are stuck with them.

    Unfortunately despite its commanding dominance and market sway, Apple has yet to really free us from the tollbooth operators, but has loosened them a bit. Google seemed to be flirting with upsetting them, but has since backed off. Of course it is really in neither of their best interests perhaps to break up those cartels.

    What we really need is freedom like with PC cars in the phone market. The OS would be like the engine. Some Android phones allow us to swap out the engine, and some manufacturers even provide engine upgrades. But other manufacturers, lock the engine in the car and do not allow us to load custom engines inside. This forces us to ditch old cars for new ones with the latest engine.

    Okay I may be pushing the analogy now...

  19. Android is fragmentation enabler by SuperKendall · · Score: 2

    Android actually reduces fragmentation. Could you imagine what would happen without Android? Every phone manufacturer would have its own completely different OS.

    This is backwards in two ways:

    1) Android is acting as an ENABLER. That is the term that is used when someone acts in a capacity to encourage another to engage in a self-destructive behavior - as in letting cell phone companies keen to "leverage" the position as the carrier you are stuck with to force-feed you apps you do not want and brand the hell out of your UI. Android ENABLES companies to do exactly that, which is real fragmentation.

    2) What would happen without Android? In the real world, if Android faded out today (no, it will not, speaking only hypothetically) you would not have each carrier with it's own OS. You would have carriers carrying iPhones and Windows phones at a minimum, probably still blackberries, possibly even WebOS devices. Note that ALL of those platforms prevent the Android fragmentation we are seeing by disallowing extensive carrier monkeying with the UI.

    Only Android is allowing carriers to go wild, and so they are - to the detriment of users, carriers and Android itself. I thought Android had a lot of promos initially but was HUGLEY disappointed that Google did not put a foot down and mandate some consistency, when they were still in a position to do so (having the only viable OS for a while to compete against the iPhone).

    Now Google cannot put that genie back into the bottle. But they can attempt to weave a spell hiding the genie and the bottle and pretending they do not exist.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:Android is fragmentation enabler by Galestar · · Score: 2
      Your argument is like saying Microsoft should mandate that Dell can't install crapware on its computers. One of the reasons Microsoft won the OS war was because is was willing to work with every manufacturer to make sure its OS ran on their hardware, similar to why Android is winning and will eventually dominate the mobile OS war. Placing arbitrary requirements on manufacturers with no legitimate technical reason can hurt the relationship between them, and as such is generally not done.

      Along the same lines, let me ask you this: is Windows "fragmented" because there are so many different hardware vendors that all install their own software? Clearly not. Why then do people say Android is "fragmented" for the same thing? The answer is that they are clearly spreading FUD. Now, if you wanted to bring up fragmentation in SDK levels or device capabilities, sure - but you don't. You are attempting to stretch the term to encompass something which it is not.

      Also, you are completely wrong about what the market would look like without Android. Let me take this statement for example:

      You would have carriers carrying iPhones and Windows phones at a minimum, probably still blackberries, possibly even WebOS devices

      iOS is only available to Apple, Blackberry only available to RIM, Windows Phone is very fresh out of the gate and WebOS is a antiquated piece of crap.

      I maintain my earlier statement that all other manufactures would use their own OS. Here is an (incomplete) list of manufacturers that would need their own OS:
      Acer
      Alcatel
      ASUS
      Dell
      Fujitsu
      HTC
      Huawei
      Kyocera
      Lenovo
      LG
      Motorola
      NEC
      Pantech
      Sharp
      Sony Ericsson
      Toshiba

      You starting to get the picture yet? A world without Android would be orders of magnitude more "fragmented" - so much so that app developers would have to completely rewrite their apps from scratch for two dozen platforms instead of the current 4.

      --
      AccountKiller