Slashdot Mirror


Android Co-Founder: Fragmentation "an Overblown Issue"

curtwoodward writes "Sure, developers might pull their hair out trying to keep track of all the versions of the Android operating system scattered across hundreds of millions of mobile devices worldwide. But a co-founder of Android says the OS's fragmentation problem is being blown out of proportion. At an event this week in Boston, Rich Miner — now a partner at Google Ventures — said some level of fragmentation is inevitable with Android's reach and the number of partners in the ecosystem. But things are getting better, he said, and in any case most consumers don't notice the difference: `This is a bit of an overblown issue, frankly.'"

77 of 289 comments (clear)

  1. Yeah. by Anonymous Coward · · Score: 5, Insightful

    This just in: Guy with stake in product says nothing is wrong with product. Film at 11.

    1. Re:Yeah. by girlintraining · · Score: 4, Insightful

      This just in: Guy with stake in product says nothing is wrong with product. Film at 11.

      Thing is, he's not wrong. Most consumers won't notice. But then, most consumers wouldn't notice if their computer ran on little gerbils inside and the internet was just a series of tubes. But that's no excuse for his handwave. Fragmentation is a problem. Maybe it's not a severe one -- maybe not yet. Maybe developers can muddle through. Maybe, even everything is fine. For now.

      But complacency will always get you a kick in the ass by the next best thing in technology, and you can go from cutting edge to curdled milk in no time at all. Iconic brand names of even a few years ago are now nothing more than sign posts in the desert -- Compaq. E Machines. 3Com. They were once all major brands and now they're dust. If you want to stay on the leading edge, you have to push the boundaries. You have to innovate, improve, refine, create. You can't talk about "ecosystems" and "platforms" like they're going to just go right on existing on their own, like they're some timeless thing.

      They won't. Android will die someday; Everything does. The only question is how long it'll last -- and if you want that question to be "For a long time yet," then you best listen to the people who work with it every day and say "This is a problem." And you'd better answer back with something better than "No it's not." Address the problem now, while it's small... because trust me when I say... if there's one thing computers are good at, it's multiplying trouble. Exponentially. Don't wait. Fix it. Fix it now. Before you're sitting on the ruined throne of a kingdom of dust.

      --
      #fuckbeta #iamslashdot #dicemustdie
    2. Re:Yeah. by viperidaenz · · Score: 5, Informative

      He never said it wasn't a problem. He simply stated it was overblown - ie, it's an issue, but not as big an issue as people (read: Apple and Microsoft) are making it out to be.

    3. Re:Yeah. by mjwx · · Score: 5, Interesting

      He never said it wasn't a problem. He simply stated it was overblown - ie, it's an issue, but not as big an issue as people (read: Apple and Microsoft) are making it out to be.

      This,

      Fragmentation is a minor issue for developers, it only crops up when you're trying to do specific things. If you target Android 1.5 then it will work on versions 1.5 to current (4.2), however if you target 4.0, your application might not work on version 2.3.

      Thats the extent of fragmentation technical issues. For the consumer, Google Play filters incompatible applications for them.

      The big problem with fragmentation is that Apple and Microsoft have nothing worse to bang on about as Android eats their lunch.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    4. Re:Yeah. by Anonymous Coward · · Score: 2, Insightful

      You had me until the last line. I don't think Microsoft has a lunch to eat here and Apple is still the one making the vast majority of the money. Quantity is a quality all its own, but come on?

      I saw this as someone who had an Android phone, liked it, but bought an Apple phone when it died. At full price (I was under contract with my carrier still) without a second thought. I'm not saying I'll never go back, but not at full price. And that's an important distinction, I think.

    5. Re:Yeah. by LesFerg · · Score: 4, Informative

      Thing is, he's not wrong. Most consumers won't notice.

      I certainly noticed when Google Chrome would not install on my android 2.3 phone, which LG refuse to provide any further updates for.
      In fact Google seem to be the most inclined to produce apps which will only run on the latest version of android and bugger anybody who hasn't thrown out last years tech and bought something new.

      --
      If I had a DeLorean... I would probably only drive it from time to time.
    6. Re:Yeah. by oursland · · Score: 3, Insightful

      Thats the extent of fragmentation technical issues.

      No, that's not correct; the problem goes further. On some devices things display differently, even though they have the same version of Android. On some devices you have access to audio/video codecs that aren't available on others.

      In the end, this lack of cohesion meant my company stopped developing their A/V application because there was too much variability, even when versions of the Android OS were the same. When this happens we lose out on a market, but the customers never get a chance to use and enjoy our applications.

    7. Re:Yeah. by mjwx · · Score: 2

      On some devices things display differently, even though they have the same version of Android. On some devices you have access to audio/video codecs that aren't available on others.

      No,

      This is when you target Android API's not vendor specific API's.

      So you really have just re-iterated my point. If you target ANDROID 2.2 it will work on Android 2.2 and above, if you target a SAMSUNG API, it may not work on HTC phones.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    8. Re:Yeah. by the_B0fh · · Score: 3, Insightful

      So close, yet so far.

      Why do you think a developer would target 4.2 when he could get a bigger market if he targets 1.5?

      So what are the main reasons he would *NOT* target 1.5? If all a developer has to do is target 1.5, then why are all the android fanbois getting a boner whenever a new version comes out?

      Please sit and think for a while. There *IS* a fucking difference between 1.5 and 4.2. And the extra functionality is expressed by new APIs which make it simpler for the developer to write stuff, and interoperate with other stuff written to that set of APIs. What havoc would it be if everyone reimplemented their own SSL layer?

      If you think really hard, you may finally understand why it's fragmentation.

    9. Re:Yeah. by the_B0fh · · Score: 3, Informative

      You don't understand what is fragmentation. In context of the Android discussion, it's not about what kind of bloatware was installed or not installed, required, or not required. It's about the different versions of Android in use. If you want to target your app at 1/3 of the Android market, you can write towards Android v4.0.

      If you want to target your app towards 3/4 of the market, you write towards Android v2.2. If you want to hit higher percentages of the market, you have to go down to earlier versions of Android.

      Obviously later versions of Android have features and functionalities you can leverage, improved security, etc. Earlier versions of Android means you have to write those yourself, or just not use that feature.

      Compare this to iOS. If you want to hit 99% of the iPhones on the market, you write towards iOS 6.0.

    10. Re:Yeah. by thesupraman · · Score: 2

      Thing is, he's not wrong. Most consumers won't notice.

      I certainly noticed when Google Chrome would not install on my android 2.3 phone, which LG refuse to provide any further updates for.
      In fact Google seem to be the most inclined to produce apps which will only run on the latest version of android and bugger anybody who hasn't thrown out last years tech and bought something new.

      Most people with smartphones are on contracts that subsidize a new phone every two years. This is a problem that solves itself.

      Should Google force every builder of Android devices to commit to updates for years? If they did this three years ago no manufacturer would have built Android hardware. If you think Android is fragmented, imagine every phone maker building their own OS.

      No, most people IN AMERICA are on contracts that INCLUDE THE COST OF a new phone every two years

      There, fixed that for you.
      When you would like to join the ranks of the thinking, not pay for a new phone every two years whether you like it or not, and therefore pay cheaper prices, feel free.

    11. Re:Yeah. by Anubis+IV · · Score: 3, Interesting

      I can't help but feel that you've been a bit out of touch with the market, since you've got facts wrong on both sides.

      First off, a correction in favor of Android and Samsung:

      There's a great deal of hardware competition in Android phones, which means no one manufacturer does the kind of volume Apple does

      Contrary to your statement, Samsung's volume is FAR greater than Apple's, though it's also split up over a greater number of models. As of April, they ship almost 2x as much, in fact. I do seem to recall seeing that the latest iPhone remains the most popular smartphone with the major carriers in the U.S., but if we're considering all smartphones sold, rather than just what's the single most popular model, and look at it on a global scale, Samsung is well ahead of Apple in terms of volume sold.

      And then, an answer to your rhetorical question that seems to be contrary to what you expected:

      Are they [Apple] making the vast majority of money?

      Last quarter (i.e. launch quarter for Samsung's flagship Galaxy S4) Apple only managed to bring in a paltry 57% of the profits in the global smartphone industry, with Samsung taking 43% (well, technically, LG came in at a hair under 1% if you look into the numbers carefully, but they got rounded out in most of the articles on the subject). Every other smartphone player is either break-even or losing money. The reason I call it "paltry" is because it's actually down from their high the previous year when they managed to capture 74% of the profits, leaving Samsung with 23%, HTC with 1%, and the rest at break-even or a loss. So, yes, to say the least, they are making the vast majority of money, though it's certainly not as vast as it was last year, since the gap has shrunk from 51% to 14%, mostly because Samsung has been doing very well and Apple has cut their profit margins by putting out devices with higher production costs (the iPhone 5 is notorious for being difficult to manufacture due to issues such as its micron-level tolerances during manufacturing and assembly).

      Anyway, there's definitely an argument to be made that the cheaper Android phones are winning massive amounts of market share, but it's like the old joke about the shop owners who are losing money on every sale but plan to make up for it on volume. The only winners in this are the ones selling the "high-spec" phones. The rest are trying to buy their way into third place and are paying for it out the nose.

    12. Re:Yeah. by LiENUS · · Score: 2

      Samsung S4, unlocked price: $699..

      Strangely enough it's actually $649 you seem to have found a vendor on amazon who is inflating the price... (or perhaps thats a 32gb model?)
      https://play.google.com/store/devices/details?id=samsung_galaxy_s4&feature=device-featured
      the htc one is a mere $599 for their 32 gb model....
      https://play.google.com/store/devices/details?id=htc_one&feature=device-featured

      What in the world are you smoking, and why aren't you sharing? Also, do you understand that the Nexus phones are sold without profit, and even support costs built in? Google themselves have said that multiple times. It's the cost of hardware, and that is it. Have a think about it. Why would someone essentially do what an a "dump" of the Nexus hardware?

      Interestingly enough the nexus phones aren't sold without profit, in fact the nexus 4 has ~$150 profit. They just aren't sold at ridiculous levels of profit... Note that price is based on a tear down and the price of components.

    13. Re:Yeah. by oursland · · Score: 2

      We developed during Android 2.2, when there wasn't all the support there currently is. Furthermore, the support we had access to involved playing URLs, well the transport stream we used does not have a URL. Furthermore, at times we may have to directly insert I-Frames into the stream, manually step the decoder, and insert discontinuities into the stream. The codecs did not support any of that.

    14. Re:Yeah. by rtb61 · · Score: 3, Insightful

      Fragmentation is never ever going to be a problem for Android because 'specifically' it is a design feature, it's called choice. The only people who consider the choices available to manufacturers and customers in Android to be a problem are, tah dah, Apple and M$ and I'll let everyone guess why, with out bothering to state the obvious.

      Yes , oh my god, Android will fragment because it was bloody designed to do so. However the will be the main 'hmmm' tine (one word as good as any other) as governed by Google in this case, around which other manufacturers will base their fork, drift away from and drift back to based upon customer feedback. Google also has the opportunity to include bits and pieces from the forks back to the main tine.

      Choice, choice, choice, those choices the manufactures make with regard to Android and the choices in hardware it is used to control and how the customers alter their choices based upon product presentation, peer reviews and experience.

      Fragmentation in Android is a problem, and it is a problem for Apple and M$ because it allows multiple development streams which can test consumer reactions for far more rapid product development and implementation, as well as of course providing customers far greater choice and of course individuality. Apple and M$ phones for people who wish to conform to their overlord manufacturers choices, who wish to look and behave exactly like their overlords designed market segments, for people who like to have the choices made for them.

      --
      Chaos - everything, everywhere, everywhen
    15. Re:Yeah. by Sockatume · · Score: 2

      That's a clear disincentive for developers to bother with the APIs implemented in Android 4.0, no? Thereby a disincentive for Android apps to stay technically competitive.

      It's bad. How bad is an open question.

      --
      No kidding!!! What do you say at this point?
    16. Re:Yeah. by Dog-Cow · · Score: 3, Interesting

      Except that doesn't really matter because most of those features are user-level features, and not a part of the SDK anyway. And Apple's support for backwards compatibility makes it trivial to handle missing features anyway.

    17. Re:Yeah. by AmiMoJo · · Score: 4, Informative

      Your mistake was expecting a relatively young OS to provide you with a codec that could do some pretty unusual stuff. You could bundle your own codec, Android supports native code for performance.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    18. Re:Yeah. by Politburo · · Score: 2

      Stock price is not relevant in a vacuum, one must consider the number of shares. This metric is called market cap. Apple is somewhere around $400b, Samsung is a bit below $200b. Investor confidence was recently downgraded for Samsung.

    19. Re:Yeah. by Kelbear · · Score: 2

      When I search for samsung galaxy s4 on amazon I get 3 offers:
      $613.49
      http://www.amazon.com/Samsung-Galaxy-I9505-white-16GB/dp/B00BTCE734/ref=sr_1_1?s=wireless&ie=UTF8&qid=1373549604&sr=1-1&keywords=samsung+galaxy+s4

      $605
      http://www.amazon.com/Samsung-i337-GALAXY-Phone-16GB/dp/B00CRO6QFA/ref=sr_1_2?s=wireless&ie=UTF8&qid=1373549604&sr=1-2&keywords=samsung+galaxy+s4

      $619
      http://www.amazon.com/Samsung-i337-GALAXY-Phone-16GB/dp/B00CRNTDII/ref=sr_1_3?s=wireless&ie=UTF8&qid=1373549604&sr=1-3&keywords=samsung+galaxy+s4

      Full price on T-mobile with no contract is $650, same for Google Play.

      I mean, there's some dumbass trying to sell one for $1300, but that's just wishful thinking, not a market price. $650 is the standard price, anything below is a discount, anything above is scalping.

    20. Re:Yeah. by LiENUS · · Score: 2

      Just thought I'd link to a tutorial on having fallbacks http://android-developers.blogspot.com/2010/07/how-to-have-your-cupcake-and-eat-it-too.html I don't think adding permissions not in v1.5 are an issue. Android 1.5 would just ignore them while newer versions with support for them would properly utilize them.

    21. Re:Yeah. by the_B0fh · · Score: 2

      Another person who cannot tell the difference between TOTAL NET PROFIT that company A makes is overwhelmingly larger than the TOTAL NET PROFIT that company S makes.

      Not that S isn't catching up, mind you. They are.

    22. Re:Yeah. by Anubis+IV · · Score: 2

      Micron level tolerances and Chinese hand assembly of components don't mix.

      You're making my point for me. I'm not the one claiming micron-level tolerances. Apple did.

      Apple has a marketing video posted for the iPhone 5 where they talk about their process and how they achieve those micron-level tolerances. It basically involves photographing the phone with a high-megapixel camera and then computationally analyzing the image of the unibody frame to select a faceplate from one of 725 minutely different shapes, in order to choose the one that will best fit the frame. But if the unibody frames are not consistent enough, then nothing will fit at all, which has been leading to poor yields and expensive manufacturing. That's on top of the expensive frame that you're talking about, and I never meant to suggest that the micron-level tolerances were the only source of reduced margins; they were merely an example.

      P.S. Interestingly when I was researching my facts for that last post, I actually ran across a number of people talking about doing machining by hand using techniques that had been available for at least 40-50 years in order to achieve tolerances of 1 micron. A couple of people even mentioned that their work involved having to go under that point, all by hand, and that they'd consider a single micron of tolerance to be a luxury, though it sounded like they were all working in scientific or engineering pursuits of a small scale that could afford to be done by hand, rather than mass manufacturing tens or hundreds of millions of devices. I'm sure other slashdotters would know more about that stuff, since I stick to software in my day job, but I found it to be rather remarkable to consider that someone could machine a product to a level of precision like that without having to involve a computer.

  2. BS by Anonymous Coward · · Score: 5, Insightful

    The problem is NOT overblown at all. There is a serious problem when there are apps that require a specific android version or device and the numbers are increasing.

    1. Re:BS by Anonymous Coward · · Score: 2, Insightful

      When you're pissing off your user it doesn't matter who's problem it is.

    2. Re:BS by Anonymous Coward · · Score: 2, Informative

      So, tell me, Mr great programmer, how can I verify that my app will run on every Android device before I release it?
      If you tell me that I need to test it on various versions of Android on several devices, I claim that fragmentation indeed is a major problem.

    3. Re:BS by thegarbz · · Score: 2

      Actually it really is. More than half of devices are on ICS or above. Most devices are on Gingerbread and above. NEARLY EVERY APP is capable of running on Gingerbread and above and those which aren't can opt to use a compatibility API or are likely trying to use a feature of the Android API to access a part of the phone that the Gingerbread user likely doesn't have (IR transmitter, NFC, hydrogometer etc).

      I never came across an app other than Chrome that didn't run on my Gingerbread phone, and when I finally cracked the phone to run ICS Chrome ended up being incredibly slow on the old hardware so I didn't run it anyway.

      As your "special apps" are increasing so are the number of users not using old hardware. As said the problem is way overblown.

  3. I disagree by twistofsin · · Score: 4, Interesting

    And I'm just an end user who owns both Android and iOS devices. When I see the disparity in app quality on both platforms, especially in games, and hear developers explain why Android is so much more difficult to work with I'm going to take it at face value.

    1. Re:I disagree by Tr3vin · · Score: 2

      The big issue with games on Android vs iOS is that Apple typically have very powerful hardware while Android devices for the most part don't. Then you have different GPU architectures, so what runs well on lets say a Adreno chip won't necessarily work on a Tegra one and vice versa. It really isn't all that different from what PC development is like if you are actually supporting Laptops & Desktops with varying chips and capabilities. I think you hear a lot of complaints from game developers because they are using prebuilt engines and those aren't always easily patched. They are great to put content together quickly but you are pretty helpless if you run into some technical issue. For example, I've seen issues with Unity and z-buffer fighting on some of my Android devices while my own custom built scene-graph renders content without issue. Inheriting other people's bugs sucks but I don't think it has anything to do specifically with the Android platform.

    2. Re:I disagree by Ark42 · · Score: 3, Interesting

      As a developer, I can say hands down that iOS is WAY more difficult to work with than Android, for completely unrelated reasons. The whole fragmentation thing is more or less something I ignore. You have basically two choices: Program to a older API, and ignore all new features, or, Program to a newer API, and ignore all older phones. I've chosen to always target Android 1.6 and my apps always have no trouble running on new phones. I've seen a feature that only exists in newer APIs that I really can't live without, so I always code around anything that requires 2.2 or 4.0, etc. It's not a big deal at all, and all the documentation is very good about stating which API a function requires, plus the Eclipse IDE will automatically show warnings for anything you try to use if you declared a target API older than something requires.

    3. Re:I disagree by BorgDrone · · Score: 2

      As a developer, I can say hands down that iOS is WAY more difficult to work with than Android, for completely unrelated reasons.

      I'm also a mobile developer (both iOS and Android) and I feel the exact opposite. What makes you say iOS is more difficult to work with than Android ? For me iOS gives me a lot more power to do what I need to do; Google made some design choices in Android in order to support low-end device, which make life a lot more difficult on Android than on iOS. On average I'd say it takes 2-3 times a much time to make an Android version of an app than the iOS version, while sometimes having to drop features because they won't work on older OSes or can only be supported on high-end devices, resulting in less polished apps.

    4. Re:I disagree by am+2k · · Score: 2

      Why would a developer care about devices that don't connect to the App Store (and thus don't get anything bought for)?

  4. Consumers may not notice ... by 0x000000 · · Score: 5, Interesting

    but I as a developer sure do notice. The biggest issue I keep running into (developing backend software for my companies frontend software) is that testing on a mix of devices means learning the quirks for every single manufacturers user interface that they have bolted on top of Android. We've also had some weird issues based upon the Android version installed, across two devices with the same Android version number (4.0 for example) with the carrier/device manufacturers changes we have a bug on one but not the other.

    This is highly annoying.

    One issue that Android users hail as the greatest thing since sliced bread (alternate keyboards) actually meant having to write work-arounds because some keyboard implementations were simply broken, or actually caused issues with entering text in certain situations. An alternate keyboard shouldn't be able to have that sort of an effect!

    Fragmentation is real, and it is an issue. Consumers don't notice because they only use a single device, developers and power users that may switch more often than the average user will notice and it is an issue.

    --
    cat /dev/null > .signature
    1. Re:Consumers may not notice ... by Ark42 · · Score: 3, Insightful

      As if those older 2.x devices would ever get a 5.x upgrade anyway, so it doesn't really matter. Just target 1.6 or 2.1 and don't worry about it. If you're running into weird issues on certain phones, you're probably programming something too specific, and not doing things right because your code is sloppy or trying to be cute. Program in a more general manner and your app works just fine on all devices.

    2. Re:Consumers may not notice ... by hsmith · · Score: 3, Insightful

      Exactly. Anyone who says fragmentation isn't an issue clearly isn't doing Android development.

      I find the platform a breeze to actually develop for. But, the issue is in testing and QA. The dearth of devices out there with hundreds of variations has created an unsustainable environment to deploy against.

      Google really should be pushing any manufactures that want to license the Android name to properly implement the APIs. Failing to do so is creating quite the issue.

    3. Re:Consumers may not notice ... by thegarbz · · Score: 2

      Can you be a bit more specific about what the hell it even means to be "programming something too specific"? That's just a vague blame-the-victim statement.

      Really you don't understand how programming something too specific works? Here's a hint. Don't assume a screen resolution. Don't layout your app interface as unscaled bitmaps. History is full of developers exploiting bugs or intricacies in the system they are developing for to make things work. *cough* IE6 *cough*. One example I saw was an audio app using some Samsung audio API. Naturally not very many 5 star ratings in the Play Store and those which were all said something like "Works fine on my Galaxy S#"

      Programming is not about walking on eggshells. It's about reading the documentation of the API and not hacking your way around APIs doing it your own way. You follow the API documentation and it's unlikely you'll ever have compatibility issues. Unless you use a fancy new feature from a newer API, and guess what there's compatibility APIs that allow you to use new functionality on old versions of Android.

  5. Re:Most don't notice the difference by MrEricSir · · Score: 3, Interesting

    Is that really true, though? There's an unfortunate tendency in the tech industry to talk down to the "average user" as though they had never even seen a computer before.

    Maybe that was useful at one point, but these days assuming your users are unfamiliar and uncomfortable with technology seems laughable.

    --
    There's no -1 for "I don't get it."
  6. Re:Most don't notice the difference by Nerdfest · · Score: 2

    Most people I know buy high-end Android phones that are either clearly the best phones on the market, or the best for the price (like the nexus 4). Perhaps that's just me though ...

  7. What improvements? by Anonymous Coward · · Score: 3, Insightful

    Google marketing: you botched this one. First you claim the improvements are amazing, then you claim most users don't even notice? Either the amazing features arn't getting used, or they are not better. Either way, I don't see how thats a good thing.

  8. Re:Most don't notice the difference by Anonymous Coward · · Score: 2, Insightful

    Is that really true, though? There's an unfortunate tendency in the tech industry to talk down to the "average user" as though they had never even seen a computer before.

    How to make sure you NEVER say that again: get a job working tech support.

    What you will say instead: "My God ... I ... I ... I had no idea..."

  9. Re:Most don't notice the difference by Microlith · · Score: 2

    these days assuming your users are unfamiliar and uncomfortable with technology seems laughable.

    They know their uses are familiar and comfortable with it, but only on the most superficial of levels. They'll happily integrate a device into their lives but don't actually understand it past the outward facing veneer. What they do is discourage further understanding via walled gardens, DRM, and other lockouts.

  10. Re:Most don't notice the difference by Anonymous Coward · · Score: 5, Insightful

    Tech support rant time:

    I did tech support initially. You will mourn for the human race (especially the race of your home country or country calling in) as a gestalt after a while after dealing with all the calls you get, day after day. To boot, a good chunk of these people have an attitude problem, as if they are proud of the fact they broke something and are getting a lackey to "fix" [1] it for them.

    Here in the US, being a loud-mouthed Luddite is encouraged. STEM and computer literacy is for outcasts, people who will never make the football [2] team.

    Of course, with the floodgates open for businesses to get cheap H-1Bs, there is never need for most Americans to even give a rat's ass about how something works or learning basic IT skills such as how not to get one's computer constantly compromised.

    Of course, this means long term the country is fucked [3] when it comes to mattering in the global scheme of things, but most Americans care more about a Jersey Shore rerun than actually trying to learn relevant skills in science and technologies.

    [1]: When I say "fix", I mean get in a state of acceptable use. This sometimes can never happen with some people.

    [2]: US football.

    [3]: I normally write fscked... but this case, the full vulgarity is the thing that works. I'd LOVE it if the us were fscked... that means we would have a consistent filesystem and working metadata.

  11. Re:Most don't notice the difference by exomondo · · Score: 2

    Is that really true, though? There's an unfortunate tendency in the tech industry to talk down to the "average user" as though they had never even seen a computer before.

    He didn't say that at all, but I do think the idea that the vast majority of Android users don't know what version they are using is true and no different to iOS users, the only reason iOS users are up to date is that they get an update notification and a button to press. If Android had a mechanism to deliver updates to all devices you'd see the same thing but the many individual carrier and OEM forks prevent that.

  12. Re:Catch 22 by CastrTroy · · Score: 4, Insightful

    How does Apple have forced obsolecense? They actually release upgrades for their phones. Even the 3GS can run IOS 6. For the new IOS 7 they're dropping support for the iphone 3GS, but that phone's getting pretty old now. Sure there will be problems with running programs that require faster processors on the old phones, but Android has the same problem. Android has the additional problem of developers having to support 3 or 4 different OS versions in order to support all the devices. Also, with Android, there's the problem that if your phone wasn't one of the popular ones, there's a lot of stuff that doesn't work with it, and finding accessories for them can be almost impossible. Even getting unofficial upgrades for unpopular phones using things like Cyanogenmod is impossible since they only support popular phones models.

    --

    Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
  13. Re:Catch 22 by Desler · · Score: 2

    How exactly did Apple choose the latter? The four-year-old iPhone 3GS has gotten all updates from iOS 3 up through iOS 6.1.3. It is only until 7 that it will no longer receive them. Many Android phones haven't seen updates beyond what shipped with the device.

  14. Re:Catch 22 by Desler · · Score: 5, Insightful

    Yeah, Apple continued to give it OS updates even after it was discontinued. That's pretty much the opposite of "forced obsolecense". I had the T-Mobile Galaxy S that shipped with 2.1 that was supposedly going to get the Android 2.2 update from Samsung "just around the corner" and yet that didn't materialize for over a year after I bought it. And then it never officially got Android 2.3 since Samsung had long since moved on to the SII.

  15. Re:Master Key, anybody? by Ash-Fox · · Score: 2

    He's correct, the fragmentation issue is quite overblown, especially when compared to Android ‘Master Key’ Security Hole Puts 99% Of Devices At Risk Of Exploitation

    Since this is to do with source signature verification which only the Google App store uses (other stores use alternative signature mechanisms) and from the article you linked:

    Update: According to a report in CIO, Google has already modified its Play Store’s app entry process so that apps that have been modified using this exploit are blocked and can no longer be distributed via Play.

    I have to concede, I agree, it is quite overblown.

    --
    Change is certain; progress is not obligatory.
  16. Re:Good by RyuuzakiTetsuya · · Score: 2

    why not just sideload?

    --
    Non impediti ratione cogitationus.
  17. More accurate by Anonymous Coward · · Score: 3, Funny

    More accurate version: "Android co-founder says that users don't notice fragmentation, because OEM customizations make the phones shitty no matter what version they are."

  18. Re:Most don't notice the difference by viperidaenz · · Score: 4, Insightful

    My wife recently bought a new phone. She didn't just want a phone that runs apps.
    She wanted a white one.
    It also had to play that god forsaken game The Croods (which works flawlessly on my 2.3 android, her 3.something tablet and her new 4.2 phone. What's this fragmentation problem again?).

    It's not a user problem, its a developer one.

  19. Re:Good by DMUTPeregrine · · Score: 2

    F-Droid for open-source apps, including ad blockers. BotBrew for a debian-like package management system.

    --
    Not a sentence!
  20. Serious problem by kbg · · Score: 4, Insightful

    The problem is that most phone vendors (basically all except Google) never update the Android system after the phone is released. This means that there are millions of phones stuck on some ancient versions of Android but many apps for Android are targeted at specific version which are constantly getting higher and higher because Google keeps pumping out new versions of Android.

  21. Re:Catch 22 by viperidaenz · · Score: 2

    But your phone doesn't get slower and slower and the OS gets upgraded.

  22. Re:Most don't notice the difference by mjwx · · Score: 3, Informative

    Because they have no clue what they are buying. They just wanted a cheap phone than runs apps.

    Which is why high end Galaxy S# and HTC One phones sell so well huh?

    Remember that a $350 Nexus 4 is in the same category as a $900 Iphone. So in that context, what you say is half true (I'd wager good money that Iphone buyers know less about phones than Android buyers), but a cheaper phone is not a crappier phone (in fact, between the Nexus 4 and the Iphone, you're getting more phone for less money).

    --
    Calling someone a "hater" only means you can not rationally rebut their argument.
  23. To everyone who thinks it is overblown... by Fosterocalypse · · Score: 4, Informative

    http://www.gamasutra.com/view/news/195310/Video_iOS_Android_myths_dispelled.php Here is a post mortem from a game developer who released two mobile games on iOS and Android. He briefly explains that both of the games ran perfectly fine on all but 3 devices. They weren't targeting a specific version of Android. They're supported devices were over 1900 devices for each game. So the fragmentation isn't as big of an issue as Apple likes to talk it up to being. And after the T-Mobile announcement today the fragmentation should only get better from here.

  24. Here is one thing that I do notice by dudeman2 · · Score: 4, Interesting

    As the owner of a non-upgradeable Android 2.3 phone (Motorola Defy XT) I find that most apps I care about work fine on the phone... with the exception of all the new Google apps and updates to said apps.

    Google Maps
    GMail
    Google Now
    Chrome
    all of these apps are either not available, or are only provided in downlevel versions. You have to be running 4.x to get the latest and greatest apps.

    Meanwhile, Google produces versions of their apps to run on iOS 6, which is available on every iPhone back to the 3GS from 2009.

    1. Re:Here is one thing that I do notice by Aggrajag · · Score: 2

      Defy XT does have an "official" update to ICS but it was only released in China. There is a guide how to flash it to your phone as well. Obviously I am not responsible if anything goes wrong.

      http://forum.xda-developers.com/showthread.php?t=1827338

  25. Re:Most don't notice the difference by AdamThor · · Score: 5, Funny

    [3]: I normally write fscked... but this case, the full vulgarity is the thing that works. I'd LOVE it if the us were fscked... that means we would have a consistent filesystem and working metadata.

    I understand that the government is working on the metadata thing...

    --
    -- "Oh. This guy again."
  26. IOS has the same problem by MarcoAtWork · · Score: 5, Insightful

    I have a still perfectly functioning ipod touch first gen where I can't basically reinstall any of the apps I own because the current versions of them in the app store are not compatible with my IOS version. If I decided to wipe it and resell it it would basically be a paperweight for anybody who purchased it as they would not be able to install anything on it.

    In the end companies should be free to EOL old versions of their OS, obviously, but there should be an official way to get versions of apps compatible with your old OS if the app existed already in the first place. If I have app foowiz 1.3 that runs just fine on OS 1.0 and recompile it to have a minor enhancement and the toolkit now makes it mandatory that I can support only OS 2.0 and up, there should be a way for OS 1.0 users to keep downloading 1.3 while everybody else moves to 1.4 and above.

    It would definitely be a lot more environmental to allow customers to keep using their old devices, or sell them (rather than tossing them) not to mention that it would make them more likely to buy more of your devices since they would trust that said devices would remain supported in the future.

    --
    -- the cake is a lie
    1. Re: IOS has the same problem by Anonymous Coward · · Score: 2, Informative

      My exact situation. I have the 1st gen iPod touch and wanted to use it purely for a pocket calorie tracker for my father. Unfortunately after wiping it clean to give to him I hit this problem. The calorie tracking app I use (version available in the app store) won't install on the latest version if the OS for this thing. It is truly worthless to me now.

      Stupid.

    2. Re:IOS has the same problem by Moof123 · · Score: 3, Informative

      Ipod Touch 1st gen came out in 2007, replaced in 2008 with second gen. So you have a 5-6 year old widget that is no longer supported, big whoop.

      The truly shameful thing about Android is that you can still buy brand new Android phones sporting 2.3.7 that were will NEVER be offered an upgrade despite being a malware magnet out of the box. Most iOS devices get several major upgrades, for years after they have been replaced, before being put out to pasture.

      I have a mix of iPods, iPads, and an Android phone, and frankly I have to say Apple does a darn good job avoiding fragmentation and avoiding the love'em and leave them feeling you get buying an Android widget. Apple is in real danger of being badly undercut thanks to their gouging for RAM and flash memory that has not budged over the time that prices have plummeted, and expectations of soared. I would like an iPhone, but frankly the level of gouging just goes too far for me to stomach.

    3. Re:IOS has the same problem by Blaskowicz · · Score: 2

      Big whoop indeed. How often do you buy some expensive shit that doesn't work after only five years? A typical computer gets about a decade of support, that's what Microsoft does at least. Even then, once the official support runs out, you can still get software running on that computer. e.g. you can download tens of thousands MS-DOS apps and games, if that's what you want. That makes the 5-year-old gizmo less capable than a 386 which is a bit ridiculous.

    4. Re:IOS has the same problem by Anubis+IV · · Score: 3, Informative

      Two quick statements, and then the rest. First, I agree fully with your comment. Second, I disagree with your subject line entirely, since the OP was describing a completely different problem than the one you're addressing.

      I agree that OSes need to be EOL'd and that there's nothing wrong with companies doing so, but that it would be far better if they wouldn't take steps to obsolesce devices before their time by making it more difficult than necessary to continue using a perfectly functional device. That said, wouldn't you agree that there's quite a big difference between EOLing your iPod touch almost two years after it was no longer on sale, and what we see with many Android phones, where they're effectively EOL'd while they're still on sale? That's the sort of problem the OP was talking about, rather than the one you discussed.

      Your iPod touch:
        Last available for purchase in September 2008
        Came with the latest version of iOS at the time of purchase
        Capable of running the latest version of iOS until June 2010

      Contrast that with T-Mobile's Android offerings, all of which are available for sale today, yet only two of them (the Nexus 4 and the Galaxy S4) out of the fourteen listed will be running the latest version of Android when you open the box of your "new" smartphone. Some of them support upgrades, of course, but not all of them, and many of those that do offer upgrades only upgrade as far as 4.1.2, which hasn't been the latest version of Android since last November. I'm sure if I went poking around hard enough, I could probably dig up some 2.3 phones that are still being sold as new today too.

      So, yes, while both Android and iOS make it more difficult to use a perfectly functional, older device than it should be, the problem being addressed here is an entirely different one that Android bears.

    5. Re:IOS has the same problem by tlhIngan · · Score: 2

      Big whoop indeed. How often do you buy some expensive shit that doesn't work after only five years? A typical computer gets about a decade of support, that's what Microsoft does at least. Even then, once the official support runs out, you can still get software running on that computer. e.g. you can download tens of thousands MS-DOS apps and games, if that's what you want. That makes the 5-year-old gizmo less capable than a 386 which is a bit ridiculous.

      Yes, but will a system from 2003 be as useful, even though the OS is still supported? Remember, you're talking about systems from the Pentium III era, 750MHz or less, with 512MB or less of RAM.

      Such a system is fairly useless today - even running a recent Firefox on Windows XP on something like that is an exercise in patience. If you can even install all you need, given the average size of hard drive is 20GB, and expansion via USB 1.1.

      And thats trying to run modern software without flaws.

      Now a PC from 5 years ago is still decent today - Core2Duo, 4GB of RAM, 250GB hard drive. Pop in an SSD and it'll still be fairly useful, but that's more a case of the user not being able to tax it than anything else - it's "powerful enough".

      Of course, smartphones have evolved rapidly the past 6 years thanks to the iPhone - before 2007, I had a nice smartphone - it had a 200MHz CPU with 16MB of RAM and ran some apps. Post iPhone though, with CPUs ramping up from 400MHz to nearly 2GHz, single to quad+ cores, RAM going from 128MB to 2GB, and from nonexistent 3D to practically console quality graphics on screens that were Half-VGA to full 1080p displays or higher.

      Of course, smartphones have now matured quite a bit and there isn't much growth left, so a smartphone from 5 years ago is fairly useless, but a smartphone from 2 years ago is pretty damn useful today. And most likely, in 2 years, today's smartphones will probably work just fine as improvements have been slim.

    6. Re:IOS has the same problem by danomac · · Score: 2

      Yes, but will a system from 2003 be as useful, even though the OS is still supported? Remember, you're talking about systems from the Pentium III era, 750MHz or less, with 512MB or less of RAM.

      Uh, maybe not such a good example. The first Pentium 4 was released in 2000 and in 2002/03 it was very common to have a 1.6 GHz P4. These are still usable today. Sure, XP (which most of them would have come with) is only supported until April of next year, but there are alternate OSs out there that can still be used on them. I still know someone that still uses their P4 from 2001. It still works, nothing is wrong hardware-wise, and with what they use it for it's still fine.

  27. Apple has people move forward. by SuperKendall · · Score: 2, Interesting

    from what you are saying it seems android is more lenient about allowing you to target old devices.

    They are, which is why software quality on Android lags iOS.

    Apple at the moment does not let you submit to the app store anything targeting anything under iOS5 (a somewhat recent change after 6.0 had been out for a while).

    This may mean some older devices drop out - but at this point the only devices out are some 1st gen iPod touches and the very first iPhone (not even the iPhone 3G which can run iOS5). That is not unreasonable and means that applications generally make use of new and advanced system features sooner rather than never.

    In a world where Android developers pretty much have to target 2.0 devices as a base, you lose some ability to use advanced features to make a better app. That is dragging down quality all over and is only going to become more of an issue as iOS framework features advance...

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  28. Re:Master Key, anybody? by Ash-Fox · · Score: 3, Informative

    Of which is the default store on the vast majority of Android devices and for most users is the only place they get their apps from.

    And resolved for 100% of them.

    --
    Change is certain; progress is not obligatory.
  29. Android has much worse problems such as... by Anonymous Coward · · Score: 2, Interesting

    ...crashes, reboots, horrible bugs that render your device unusable.
    So, yeah, he's right, that one problem is not significant when compared to these.

  30. OS fragmentation vs many different OS by codemachine · · Score: 4, Insightful

    Sure, Android fragmentation is a real issue. However, before Android, just about every phone manufacturer had its own operating system, and it was difficult to do development for.

    It isn't like if Android didn't exist, everything would just run iOS. If Android didn't exist, we'd likely have a situation where every vendor has their own entirely different platform. That'd be real fragmentation in the phone industry.

    Right now, Android is much like Windows. You don't know exactly what version a user will have, and what hardware and configuration they'll have, but at least there is a set of common APIs you can rely on. Thanks to majority market share, you can develop an Android app and get a massive chunk of the market, even if that app needs some code to deal with specific versions of Android.

  31. No discount for paying up front by tepples · · Score: 2

    AMERICA is the home country of both Google and Dice Holdings. And the big three carriers IN AMERICA refuse to give a discount on service for not taking a subsidized phone.

  32. Well, I can tell you're not an Android developer. by Max+Threshold · · Score: 3, Informative

    Fragmentation on Android is a huge problem. Each device manufacturer has their own slightly different version of the OS, each with its own set of issues and incompatibilities. Sure, they only crop up when you try to do specific things... like, say, open a Bluetooth socket.

    (I am an Android developer responsible for testing my company's product on dozens of different tablets.)

  33. Re:It is noticed. by SuricouRaven · · Score: 2

    Most consumers are ignorant of technology. They don't know what firmware is, or even an OS.

    They'll notice 'Oh noes, my new game won't work!' But they won't know why. Even if the phone is upgradeable, they won't realise this is an option. That's why many phones include some form of automatic updater.

    Most consumers don't look at upgradeability, or even specifications, when deciding on a phone. They buy on two criteria: Does it look cool, and is it fashionable?

  34. Re:Well, I can tell you're not an Android develope by AmiMoJo · · Score: 4, Insightful

    Simply not true. Compatibility issues are almost always down to differing hardware/drivers. That's the same on any OS except for iOS where Apple tightly controls the hardware too.

    I've done Android development for an industrial product using Bluetooth. Didn't see any issues, the API is stable and just works. If I ever do discover a device that has issues I'd first assume it was down to crap hardware, not the OS.

    --
    const int one = 65536; (Silvermoon, Texture.cs)
    SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
  35. Re:Sometimes the bare bones API is insufficient by Xest · · Score: 2

    The same thing we've always done when developing on Windows, Linux, and even the web with browsers all of which have even greater degrees of fragmentation than Android even though we've never made much of a fuss about it on these other development platforms.

    If you can't deal with this problem and think it's somehow unique to or worse on Android then you shouldn't be programming because your knowledge is insufficient to the point of being dangerous.

  36. Re:Most don't notice the difference by PPalmgren · · Score: 2

    On your comment about Iphone buyers being less knowledgeable than Android buyers, I think you're right but for the wrong reasons. People who get sucked into the apple garden have a different approach when buying a device. It becomes "which Apple product should I buy?" The distinction becomes clear if you ever read the comments in an Apple review. Its purely brand loyalty. I find it dissapointing to see intelligent people get stuck in the stockholm syndrome that is Apple, but think the reason is more behavioral than intelligence related.

  37. Re:Not a problem? Please update my HTC Phone by Politburo · · Score: 2

    Sounds like an HTC problem, not a 'fragmentation' problem.

  38. Re:Consumer don't notice the app never offered ... by tlhIngan · · Score: 2

    If you are a consumer and you have a 4 year old version of Android on your phone, you will not exactly be shocked that it wont run apps that need a new phone. If you cared, you would upgrade. People with 2.1 are not going to buy your app.
    Fragmentation would be if people were launching products with wildly different versions of the OS: eg with HTC or Samsung's own APIs. Yes they do have manuf specific APIs. just dont use them and you will be fine. The generic APIs will be there and work.

    You do realize that... you can get Android phones shipping with Gingerbread today, right?

    These aren't ancient Android phones running Gingerbread because the user hasn't upgraded (in fact, most people upgrade phones when their contracts expire - because if you're taking on a new contract, you might as well get a new phone!). They're running ancient Android because that's what they shipped with! And what carriers are pushing out.

    Basically, the Android phones that move are the free ones (++ Android Fragmentation - for making phones available in a wide range of pricing, -- Android Fragmentation for making crap-droids with crappy UXs possible), and why not? Featurephones cost just as much as a smartphone these days (i.e., free), and the lower end free crap-droids you don't even need a data plan for.