81–90 of 189 posts
> My POV is ... Apple leads the Mobile OS market share ... by a huge margin. I'm having a really hard time understanding this statement. Does the author mean with respect to how updates are handled? It clearly cannot mean in terms of sheer number of installs, Android is clearly _leagues_ ahead of iOS in that regard.
The article concludes, as far as I can tell, it isn't fragmented, it just has a bunch of recent enough versions on similar enough devices to run most apps. Apps don't care what version of Android you run, they care what API support you have, and apps can detect API support at runtime and adapt. OTOH, the article fails to mention that Apple refuses to let you support devices after EOL, and even some of the oldest Andr…
OTOH, the article fails to mention that Apple refuses to let you support devices after EOL, and even some of the oldest Android devices in existence can run even the newest Android, as long as you're willing to upgrade the ROM yourself. The 2012 iPhone 5 is the newest unsupported iPhone. Would you really want to support a phone that old and have to support both a 32 bit and a 64 bit version of your app?
Something that doesn't get talked about as much is the differences between how manufacturers customize their OS. It has been talked about a fair bit on HN ( https://dontkillmyapp.com/ ), but it really is a huge problem. I can be listening to music on my phone and One+ will just kill Pandora, or Spotify. I have to manually "lock" music apps and workout apps in One+'s task switching UI to keep them from being randomly…
I don't think a lot of people understand how apps run in the background on Android. I know having worked on one recently, coming from iOS, I had a lot of assumptions about what it would or wouldn't be doing... and they were all wrong (of course). Turns out Android, at least however this app is setup, maybe by default, leaves the app fully running. Like zero effort to suspend it automatically. A part of the UI crashed…
Well, if you remove all iOS versions with https://i.imgur.com/0Ar0ta5.png My point being: there ARE other iOS versions in use. I have a backup working iPhone 4 turned on right now. It won't upgrade beyond iOS 5 (I think it's iOS 5). But somehow the author ignores all those 0.1% iOS versions, yet shows them for Android (with 4 decimals no less).
By the way: iPhone 4 supports iOS 7.1.2, released 4 years after the iPhone 4.
Earlier quoted context omitted.
It sounds like you're rolling with whatever Google's latest 'solution' to fragmentation is, so of course it's not going to be an issue: Google is dropping old devices for you so they never even appear in your console stats.[1] This is a perfectly valid business decision to take on your end, but it doesn't mean that the problem doesn't still exist... only that you aren't having to deal with it. I've got several still…
Out of curiosity: did you ever tried using Yalp store for downloading the apk from the store? Would it be useful for you?
Earlier quoted context omitted.
By the way: iPhone 4 supports iOS 7.1.2, released 4 years after the iPhone 4.
I'm not sure why the GP said his iPhone 4 won't upgrade past iOS 5, but it's worth noting: while an iPhone 4 can be upgraded to iOS 7, actually doing so is a bad idea unless you want your phone to run slow as molasses. You'll be much better off on iOS 6 or 5. (I suppose there may be a security argument for upgrading as far as possible, but it's not like iOS 7 is up-to-date either. If you're concerned about security,…
I'm not a professional app developer. A year ago I invested few months to develop an app I wanted to have. Today it has few thousand users. Fragmentation doesn't bother me. Yes, on some devices the app crashes, on others the sound lag is unbearable. I don't really care, as long as it works fine on most devices. Two things infuriate me, though. Enough to never again spend another minute developing for android. Every t…
> The second thing is recent requirement to provide 64-bit version of each app. My app depends on framework written in C++ with additional libraries in C. I can't and won't spend time to get the build for 64-bit version working. Google sent me a mail that "All new apps and app updates are required to provide 64-bit versions of any 32-bit native code they provide". So I won't be able to update existing app to existing…
I don't care about 64-bit devices. I'm fine with them not being able to install or run the app, if that's how it is. People with 64-bit devices can easily afford better products that my app tries to replace. I don't own device to test the 64-bit version, and I don't know anyone who does.
I care about existing users. I kept minimum SDK version as low as possible so that my app might reach all the cheap phones in poorer parts of world. It actually works today across many different devices, so what has changed?
Something that doesn't get talked about as much is the differences between how manufacturers customize their OS. It has been talked about a fair bit on HN ( https://dontkillmyapp.com/ ), but it really is a huge problem. I can be listening to music on my phone and One+ will just kill Pandora, or Spotify. I have to manually "lock" music apps and workout apps in One+'s task switching UI to keep them from being randomly…
Eventually I stumbled on the "Lock" feature, which as far as I know is specific to OP, and that solved everything. I'm pretty annoyed with OP about it to be honest. Android has app-specific battery optimization settings built in but they just completely ignored them.
I've been tracking the data from Google's Android dashboards over time : https://www.bidouille.org/misc/androidcharts From these observations, it seems that Android's fragmentation is getting worse, and that newer versions of Android have more and more trouble establishing themselves as the dominant version. In fact, JellyBean was the last version to reach more than 50%.
Users have absolutely no say! Planed obsolence does.
every single device could be running the latest version just fine. But the manufacturer intentionally decide to not offer (or allow!) the update on not cases.
This is pure greed over consumer rights (or respect).
want the latest security patch on your 2yr old $600 device? too bad, trhow it in the landfill and buy a new one (often with worse features)