Study suggests iOS fragmentation worse than Android


Recommended Posts

It?s that time of month again: Android?s platform distribution numbers are up for the period ending September 1, and things are looking pretty good. Android 2.1 is up to nearly 41.7% of the market, and 2.2 checks in at 28.7% ? between the two, 70% of Android phones are running 2.1 or better.

and_frag_sept1_thumb.png

Android 1.5 and 1.6 still measure at a combined 29.5% of all devices. Obviously, any number above 0 isn?t good, but as long as the rate is dropping, we?ll take it.

and_frag_sept1_2_thumb1.png

In early August, we found some data from Chitika which suggested that fragmentation is worse in iOS than Android. Given the continued consolidation of the Android, it?s not surprising to see that iOS fragmentation is still substantially worse than that of Android.

iOS_frag_thumb.png

Interesting stuff indeed, although the mandatory disclaimer: the Chitika data is a sample, whereas the Android data is from the population.

Original Article

Article is a bit silly as point releases from Android are different from point releases on iOS. The sub-point releases like 3.1.2 and 3.1.3 should be categorized together as they're bug fix releases that have no bearing on the minimum requirements for apps in the App Store. Hell, all 4.0.1 did was adjust the signal bars.

iOS 3.2 is also an iPad limited release. Something more accurate would be:

3.x.x: 31.82%

3.2 (iPad only): 12.72%

4.x.x: 34.05%

other: 21.42%

I believe this study may have been done before iOS 4.1 was released

And @ Giga even with those figures re-adjusted it still doesn't paint iOS in a light any more favourable than that of Android, so in reality the old iPhone fan argument of "Android is far too fragmented" no longer applies.

I think complaining about Android "fragmentation" is a bit stupid. Since when was having multiple OS versions considered fragmentation, especially when newer OSs are backwards compatible. Is Google supposed to stop improving Android? "Hey look, we just shipped Froyo, lets take a year off and let manufacturers update their handsets and let the competition surpass us."

I believe this study may have been done before iOS 4.1 was released

And @ Giga even with those figures re-adjusted it still doesn't paint iOS in a light any more favourable than that of Android, so in reality the old iPhone fan argument of "Android is far too fragmented" no longer applies.

It applies. Just because iOS has demonstrated fragmentation (there is still an issue with the sample, but assume it's fair) doesn't instantly mean that Android isn't fragemented either. It means they're both fragemented, and furthermore, what fragementation means is also specific to each platform. There's not as wide a variety of hardware on iOS devices for example.

From a developer's perspective, the actual OS version isn't where fragmentation is a problem. As a developer, you choose the oldest OS version you want to support and make sure your app works on that, optionally adding stuff that's only available in newer releases.

The fragmentation that's difficult is the amount of different devices are there, with different amounts of memory, CPU, display resolution, etc. That is a pain in the ass, because you have to account for everything in development and testing.

At least with the iPhone/iPod touch, the hardware is updated once a year, and in a way that at least helps developers a little bit. Yes, it's still a pain in the ass, but nowhere near as bad as it is with the Android market. The retina display on iPhone 4 and the new iPod touch is exactly twice the resolution of the older devices, meaning artwork can be pixel doubled and look respectable.

tl;dr: OS version fragmentation is a lot less important than hardware fragmentation on mobile OSes.

I think complaining about Android "fragmentation" is a bit stupid. Since when was having multiple OS versions considered fragmentation, especially when newer OSs are backwards compatible. Is Google supposed to stop improving Android? "Hey look, we just shipped Froyo, lets take a year off and let manufacturers update their handsets and let the competition surpass us."

Agreed, it is the manufacturer's faults. The simple economics of wanting to sell new handsets takes over. Besides, I have never actually ran into an application designed for older versions of Android that didn't work on newer versions, it is mainly a developer's issue and they seem to be coping with it well.

It applies. Just because iOS has demonstrated fragmentation (there is still an issue with the sample, but assume it's fair) doesn't instantly mean that Android isn't fragemented either. It means they're both fragemented, and furthermore, what fragementation means is also specific to each platform. There's not as wide a variety of hardware on iOS devices for example.

Not in the sense I was referring to. Because most iPhone fans try and use it as an argument to infer why the iPhone has superiority over Android, and this makes it obvious that does not apply

From a developer's perspective, the actual OS version isn't where fragmentation is a problem. As a developer, you choose the oldest OS version you want to support and make sure your app works on that, optionally adding stuff that's only available in newer releases.

The fragmentation that's difficult is the amount of different devices are there, with different amounts of memory, CPU, display resolution, etc. That is a pain in the ass, because you have to account for everything in development and testing.

At least with the iPhone/iPod touch, the hardware is updated once a year, and in a way that at least helps developers a little bit. Yes, it's still a pain in the ass, but nowhere near as bad as it is with the Android market. The retina display on iPhone 4 and the new iPod touch is exactly twice the resolution of the older devices, meaning artwork can be pixel doubled and look respectable.

tl;dr: OS version fragmentation is a lot less important than hardware fragmentation on mobile OSes.

Fair enough. But this isn't really Android's fault. Blame the manufacturers that make the half-assed phones. Even if Google were to institute a policy with regards to minimum specs, they could only be applied to "with Google" phones and not any device made with the open source project. I guess one of the biggest advantages of an open source project is also a major disadvantage; anyone can do anything.

Fair enough. But this isn't really Android's fault. Blame the manufacturers that make the half-assed phones. Even if Google were to institute a policy with regards to minimum specs, they could only be applied to "with Google" phones and not any device made with the open source project. I guess one of the biggest advantages of an open source project is also a major disadvantage; anyone can do anything.

If Google where also more aggressive about licensing their apps like Youtube, the Market ETC to handsets that didn't meet the requirements that would also reduce their appeal to the point that manufacturers would stop producing them. However, the pitfall of completely cutting out the budget sector of the market is that it would actually hit manufacturers hard, as they actually make more money from the budget segment than the premium segment due to the larger volume of purchases.

Besides, with a few modifications (like the removal of the 3D launcher with the older version) newer versions of Android can still be made to run on old devices like the G1 and Magic, most of the problems are caused by manufacturer apathy.

Article is a bit silly as point releases from Android are different from point releases on iOS. The sub-point releases like 3.1.2 and 3.1.3 should be categorized together as they're bug fix releases that have no bearing on the minimum requirements for apps in the App Store. Hell, all 4.0.1 did was adjust the signal bars.

iOS 3.2 is also an iPad limited release. Something more accurate would be:

3.x.x: 31.82%

3.2 (iPad only): 12.72%

4.x.x: 34.05%

other: 21.42%

Apps definitely look for specific versions. Pretty sure netflix only runs on 3.1.3 or higher, for example.

Fair enough. But this isn't really Android's fault. Blame the manufacturers that make the half-assed phones. Even if Google were to institute a policy with regards to minimum specs, they could only be applied to "with Google" phones and not any device made with the open source project. I guess one of the biggest advantages of an open source project is also a major disadvantage; anyone can do anything.

well, it's not about blame throwing, it's a fact that the Android platform is far more fragmented than the iOS platform, due to the differences in the hardware platform, not OS versions, since all the OS versions are mostly backwards compatible anyway.

It means when you look at an Android app, a lot of the times you won't be sure if it will run, or run well at acceptable speed, on your particular $300 Android device. But when you look at an iOS app, most of the times you'll clearly know whether it will work well or not on your old iPhone original.

That's not Google's fault, sure, but that's still a fact, and a fact that can have impact on both developers and customers alike. So I guess the "Android platform is too fragmented" argument is still valid.

The differences between 3.1.2 and 3.1.3 on OS are hilariously small, I think it was one minor bug fix. The same with 4.0 and 4.0.1 which was just the signal bar change. The core feature set and APIs are EXACTLY the same.

To compare it to Android fragmentation you'd need to compare 3.0 and 3.1 versions/4.0 and 4.1, when actual features were added.

Comparing minor version fragmentation to major version fragmentation is retarded :p

The funny part is my iPod touch from 2008 runs iOS 4.1 without jumping through hoops, while my 2010 HTC Legend still hasn't been updated to Android 2.2. If things stay this way in the Android landscape I'm seriously doubting I'll get an Android-based phone next year.

See, my iPhone still runs on 3.13. I would update to 4.x just it's so much damn work. When I updated to 3.13 from 3.1 it took me about 10 hours of non dedicated work to get my phone back to how it was.

Fair enough. But this isn't really Android's fault. Blame the manufacturers that make the half-assed phones. Even if Google were to institute a policy with regards to minimum specs, they could only be applied to "with Google" phones and not any device made with the open source project. I guess one of the biggest advantages of an open source project is also a major disadvantage; anyone can do anything.

You just explained why it is their fault. They are giving too much power away to the hardware manufacturers. The OS should be able to be updated straight from Google and not through the hardware manufacturer. If it breaks something with the custom UI the hardware manufacturer put on the phone then tough ****.

What google should be doing is to be forcing the hardware manufacturers to do their custom UIs using only widgets and a themeing program in Android where they can only graphically change the OS.

You should never be dependent on the hardware manufacturer for an update to the operating system.

You just explained why it is their fault. They are giving too much power away to the hardware manufacturers. The OS should be able to be updated straight from Google and not through the hardware manufacturer. If it breaks something with the custom UI the hardware manufacturer put on the phone then tough ****.

What google should be doing is to be forcing the hardware manufacturers to do their custom UIs using only widgets and a themeing program in Android where they can only graphically change the OS.

You should never be dependent on the hardware manufacturer for an update to the operating system.

To be honest, trying to strong arm the manufacturers would be of little benefit to Google. Because the commercial success of Android depends a lot on the revenue from the integrated search and advertising, it wouldn't make sense for them to try and force handset makers into designing to spec. As the Android platform is an open platform, the worst Google could do would be to refuse licensing for the closed source Google apps, they can't physically restrict access to the OS because of its open nature.

And to be honest, it seems to be working for them as is, Android is gaining market share at a vast rate, and most consumers don't seem to be bothered by the supposed "issues" because Android is continuing to accelerate in terms of market growth

One - Android phones are available on almost all carriers, making the overall number much higher, since more people can purchase it.

Two - Verizon in the US constantly runs a buy one get one free special on Android phones, thereby doubling the sales for the phone.

Three - iOS "fragmentation" is based simply on the fact that either the latest version is not available for the hardware (too old) or people haven't upgraded yet. In the second case, it's a customer issue, not an Apple issue. On the Android side, it's a case of either the hardware is too old to support the latest version or the manufacturer hasn't provided an update to the phone (or may never, depending on the phone type). This is a serious issue, since as Google updates the OS, people will tend to fall further and further behind the curve. While this may not be a large issue for mom and pop right now, it can be a problem when the latest version of Angry Birds requires 2.2 and it's not available for their phone.

As for rooting the phone and loading a cooked ROM, good luck getting mom and pop to understand what you are talking about. they just want their phone to work with whatever the latest version of their favorite app is. If that's broken, then you've failed.

To be honest, trying to strong arm the manufacturers would be of little benefit to Google. Because the commercial success of Android depends a lot on the revenue from the integrated search and advertising, it wouldn't make sense for them to try and force handset makers into designing to spec. As the Android platform is an open platform, the worst Google could do would be to refuse licensing for the closed source Google apps, they can't physically restrict access to the OS because of its open nature.

And to be honest, it seems to be working for them as is, Android is gaining market share at a vast rate, and most consumers don't seem to be bothered by the supposed "issues" because Android is continuing to accelerate in terms of market growth

You can't deny that it wouldn't be a benefit to the end users. End users could still do whatever that they wanted to the OS but you won't have to wait around for months for the manufacturer to get around to updating it. Plus it would give your device a longer life span without having to rely on another party to do their thing with the OS.

Google already restricts access to their google apps for unapproved devices which includes anything that doesn't have a 2G or 3G antenna.

Android IS doing very well but there are things such as this that would make the platform better.

This is a serious issue, since as Google updates the OS, people will tend to fall further and further behind the curve. While this may not be a large issue for mom and pop right now, it can be a problem when the latest version of Angry Birds requires 2.2 and it's not available for their phone.

Not true at ALL. My Galaxy S still has 2.1 Eclair and Angry Birds beta runs without a single problem.

As for rooting the phone and loading a cooked ROM, good luck getting mom and pop to understand what you are talking about. they just want their phone to work with whatever the latest version of their favorite app is. If that's broken, then you've failed.

Why would they need to know about rooting and custom ROMS? That's for us geeks. It's just like you wouldn't expect them to know what jailbreaking is, something that radically changes the capabilities of an Apple device.

You can't deny that it wouldn't be a benefit to the end users. End users could still do whatever that they wanted to the OS but you won't have to wait around for months for the manufacturer to get around to updating it. Plus it would give your device a longer life span without having to rely on another party to do their thing with the OS.

Google already restricts access to their google apps for unapproved devices which includes anything that doesn't have a 2G or 3G antenna.

Android IS doing very well but there are things such as this that would make the platform better.

How many smartphones do you know that don't have an antenna capable of that?

Who really cares? There is going to be fragmentation no matter what, no way around it. New features become available that older phones cannot support. Same thing happens with PC software. I still have the original myTouch and have had it for a year. Yea, I have froyo installed but I notice some problems. Why? Because FROYO was not meant for the myTouch.

Hope the myTouch HD rumors with a dual processor are true....

How many smartphones do you know that don't have an antenna capable of that?

Not smartphones, tablets. They restrict their first party apps based on whether or not it's specifically a phone or can act as one. So they already restrict the usage of their open source software depending on the hardware. Even though the OS is doing real well, I just do not see any possible benefit to the end user to force them to have to get OS updates from the hardware manufactuer. I don't get Windows updates from Dell, HP, or Asus.

It's my only beef with the OS.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Motrix Next 3.9.6 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.6 changelog: New Features Clipboard management — App-owned copy actions no longer trigger the Add Task auto-detect popup. aria2 input compatibility — Multi-line aria2-style task input is supported for URLs with per-task options such as out=. BitTorrent IPv6 DHT — Added IPv6 DHT support and related configuration. File category URL patterns — File category rules can match URL patterns with validation and localized hints. Task status tags — Added clearer waiting and sharing states for task cards. Download event bridge — Added an aria2 WebSocket event bridge for faster download notifications. Improvements Improved task list transitions and preserved task state during tab switches. Kept RPC origin access enabled for local integrations. Restored AppImage stripping in release builds after beta validation. Added localized preference guidance across supported languages. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Segra 1.6.2 by Razvan Serea Segra is a free, open-source OBS-powered game recorder offering fast gameplay capture, instant clips, AI highlights, deep game integration, and seamless uploads—perfect for gamers, streamers, and content creators. Lightweight, fast, zero bloat. Segra key features: Automatic Game Recording: Begin capturing gameplay the moment your game launches, with zero manual setup. Instant Clipping: Save important moments instantly using a customizable hotkey—perfect for highlights, montages, or quick shares. Segra AI Highlights: Let Segra automatically detect kills, assists, deaths, and key events to generate polished highlight reels without manual editing. Gameplay Uploads: Upload recordings and clips directly to Segra.tv for fast sharing and cloud access. Deep Game Integration: Enjoy advanced game-data tracking across hundreds of supported titles, enabling smart highlight generation and stat-informed clipping. High-Performance Capture: Record up to 4K at 144 FPS using OBS-powered technology with minimal performance impact, supporting NVENC, AMD VCE, and custom quality controls. Segra Editor: Edit recordings easily with timeline controls, segment management, and event-based navigation to build the perfect clip. Customization Options: Adjust hotkeys, output formats, storage paths, codecs, capture quality, and performance settings for a tailored recording experience. Segra 1.6.2 changelog: UI: Improved the transition from the loading skeleton to the real content card. Security: Added Segra.dll code signing and automatic VirusTotal upload. Settings: Fixed the settings header to highlight Account when scrolled to the top. Recording: Updated OBSKit.NET to 1.4.1. Download: Segra 1.6.2 | 74.5 MB (Open Source) View: Segra Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Hey Google, these are the Gemini features I want in 2026 by Aditya Tiwari Google Gemini has been around for over three years. The AI chatbot started its journey back in 2023 (as Bard) when ChatGPT was already a talk of the town. However, it quickly attracted criticism after misrepresenting facts about the James Webb Space Telescope. The search giant spent a year fine-tuning Bard before rebranding the chatbot and its underlying generative AI model to Gemini, drawing inspiration from NASA's first human spaceflight program. Note that Bard was initially powered by LaMDA and PaLM 2; Google has since added several new features and integrations to Gemini. That said, there is scope for improvement and a gap for new features. I have been using Gemini for a while now and have realized that the chatbot lacks several features, making it harder for me to research across topics. These are mostly function-over-form updates that can improve the overall experience. Delete individual messages from a conversation Image via DepositPhotos.com One good thing about Gemini is that it can maintain context throughout the conversation. But things might get chaotic when you want to ask a related question, but don't want it to be part of your conversation in the long run. You can't ask that related question in a fresh chat because Gemini will lose the active conversation context of what you're trying to research. If Google allowed you to delete individual question/answer pairs, you could simply ask about a sub-topic and remove it from the conversation to create a smooth flow of important stuff. Offline mode Image via DepositPhotos.com A big pain of using Gemini daily is that everything loads from the cloud. It takes time for your chats to appear, and you can't view your conversation history while offline. To get a better idea, you can open the Gemini app and see how it looks without an internet connection. While Gemini models run in the cloud, it wouldn't hurt if Google could store chats (at least the text part) on the device so we can refer to them when offline. Google can also offer a lightweight version of its AI model to help with basic drafting, summarization, and other tasks. It has the Gemini Nano model, which can perform on-device processing on Google Pixel, Samsung, and some other Android brands, but it's a system feature and not related to the cloud-based Gemini app. Make temporary chats permanent I can't thank Google enough for taking the time and effort to add incognito mode or temporary chat mode to the Gemini app. It lets you have conversations without worrying that the topics will end up in your chat history or used for model training (at least on paper). Google claims that it doesn't use your temporary chats to "personalize your Gemini experience or train Google’s AI models." However, the data is stored "up to 72 hours to respond to you and to process any feedback you choose to provide." That said, I often start researching something in a temporary chat, only to realize the chatbot's answer is good enough to refer to later. Sadly, Gemini doesn't have an option to make such temporary chats permanent. In other words, I won't be able to follow up on it if I close the temporary chat. I'm left with alternatives like copying the answers into notes or another app. My digital life will get a lot better if Gemini gets a button to make temporary chats permanent. Collapse answers for a cleaner view You're heavily invested in your research game and suddenly feel the need to go up in the chat to recall something. This is when the conversation thread starts to feel like an overwhelming, unending wall of questions and answers. What if Google added a way to collapse Q&A pairs in the Gemini chat thread? It would look quite clean and easy to navigate. You'll quickly get an overview of everything you have discussed with the chatbot. Add buttons to jump between messages Suggested mockup of the feature. This reminds me of a small but useful Gemini feature that Google could add to its chatbot: the ability to hop between prompts in a conversation. Just add simple up- and down-arrow buttons, similar to YouTube Shorts, so people can quickly scroll through the messages. A table of contents or Chat Overview It's hard to get a bird's-eye view of everything you have discussed with the chatbot during a lengthy conversation. This is where a table of contents, or Chat Overview, displayed at the top of the screen, possibly in a drop-down button, might come in handy. You'll be able to get an overview of the chat and jump between messages, serving as an alternative to the up/down arrow buttons. Temporary mode for Gemini Live Image: Google You can use Gemini Live to have real-time conversations with the chatbot, which feels like you're talking to someone in the same room. However, a downside is that Gemini Live doesn't work in Temporary Chat mode, so all your conversations end up in the chat history. Google should consider expanding the temporary chat mode to include Gemini Live. Default to a specific chat One thing that feels somewhat annoying to me is that Gemini always opens in a new chat, whether on web or mobile. Sometimes, you want to return to your last chat. Google can take cues from web browsers, which let you choose whether you want to go to a new tab or a specific web page(s). Gemini can also have options to default to a specific chat when reopened. That said, generative AI chatbots have endless possibilities given the vagueness of their work. You can mold them the way you want by attaching different connectors, adding custom instructions, and including source files. It remains to be seen what Google has in store for future updates and whether anything from this wishlist gets the green light. The search giant released a stream of new Gemini updates in recent months, including Gemini 3.5 Flash and Gemini Omni Spark, adding that it now has 13 products with more than a billion users each. What do you want to see in the Gemini app? Tell us in the comments.
    • Thank you for the post. Just a FYI that links to an outside site or promoting specific software is considered spamming here. Asking general questions is fine.
  • Recent Achievements

    • Conversation Starter
      sumytbe earned a badge
      Conversation Starter
    • One Year In
      B4dM1k3 earned a badge
      One Year In
    • One Year In
      DarkWun earned a badge
      One Year In
    • Dedicated
      Almohandis earned a badge
      Dedicated
    • Dedicated
      JuvenileDelinquent earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      507
    2. 2
      +Edouard
      181
    3. 3
      PsYcHoKiLLa
      86
    4. 4
      Michael Scrip
      78
    5. 5
      Steven P.
      76
  • Tell a friend

    Love Neowin? Tell a friend!