iOS lacks many features that have been standard on Android for years and the only reason it feels so smooth is because the UI thread has pretty much the highest QoL that anything can ever have. iOS would rather drop your network call than drop a single frame.
Android variants all have things that iOS can only dream of having in five years (notifications was a fun one), just spread very unevenly throughout manufacturers. Samsung currently has a very good Android build.
When I switched from Android to iOS in 2016, I was shocked at how little was different, and I can only assume gulf has narrowed since then. A lot of features Android users just assume iOS users don't have are there: vendor-agnostic password manager integration, Safari browser extensions, Safari content (ad) blocker API (Chrome is restricting ad-blockers soon!), more complete home screen customization and widgets, lock screen customization and widgets (iOS 16, upcoming), custom third-party keyboards, grouped/customizable notification system, native console wireless controller support from all three consoles.
Features like granular privacy controls and screen recording (with the exception of some obscure Android OEM builds) debuted on iOS first.
I'd be skeptical with anyone declaring either platform "best," I think they're both roughly equivalent.
However, I do think that anyone who uses macOS is insane to go with Android. There are simply too many useful integrations between the platforms to ignore, combined with the fact that, even if the iPhone isn't the best phone, it's usually in the top handful of choices in terms the overall package.
Sometimes it's the little things that matter. The single most used app on all my Android phones I've ever had is Kindle. And one feature that I absolutely demand from any phone is that I can flip pages with volume buttons - when reading for long periods of time, it is much more convenient than swiping with your thumb. On Android, pretty much all the reader apps can do it. But, so far as I know, this is outright impossible to implement in iOS.
Personally, I don't think the OS should ever allow an app to hijack the physical volume buttons or other hardware buttons on a phone. That seems like an avenue for abuse.
(Tip: you can tap the screen on the right side to go to the next page.)
Personally, I think that my phone should be convenient for me to use.
I'm well aware of different ways to swipe pages. The reason why the hardware volume buttons are so convenient for reading is because you just put your thumb on the volume/page down button, and you no longer have to move it at all - only press down slightly every now and then. It's much more ergonomic for long-term reading than having to raise the thumb every time, even to tap.
That seems like a really small benefit at a potentially high cost, at least to me.
You can imagine that someone might create malware or otherwise hostile app that plays a loud/embarrassing sound and hijacks your volume buttons.
Having to lift a finger to turn a page seems like a really small problem in comparison to that one.
Smartphones are general purpose devices and have to make tradeoffs like this all the time. They can't just greenlight every useful function that every type of app might want. IMO if you want an e-reader, get an e-reader.
For example: Let's say I'm a private detective. It might be nice for there to be an app that records audio and video at all times without any visual indication of my phone doing so. However, having that kind of OS level permission available to apps on an app store is probably a bad idea. I'll need to go out and buy a dedicated recording device.
Sure, we can argue about where the line gets drawn. If you like Android for allowing apps to modify hardware buttons, fine. But, I would prefer a device where physical buttons perform consistent functions. A middle ground might be some kind of buttons dedicated toward custom or app functions – but, to me, why bother when the entire screen is a customizable button?
All I can say is that I've been using Android for well over a decade now, and not once have I seen malware that hijacked volume buttons. It might actually be a permission the app has to request - I don't remember.
Either way, this was meant as an illustration of how small factors can affect decisions. I have had an iPhone as my primary phone for a few months, and this one thing was the single biggest issue I had with it at the end of the day - not that there weren't others, and some were actually more annoying when they happen, but this one is at the top because it's something that's constantly in my face. Thus, I'm not going to buy another iPhone for this reason alone; my response to "you're holding it wrong" is "you're making them wrong".
iOS’s security was praised by GrapheneOS’s creator many times - I believe according to him the best choices for a secure mobile at the time of writing was GrapheneOS on the latest pixel OR an iphone.
So you want icons to be able to overlap each other, or be different distances from each other, or what? I'm trying to figure out what exactly you're trying to accomplish. What would be the benefit of totally arbitrary, down-to-the-pixel placement ability?
Just talking about being able to grab an icon and position it anywhere I want on the screen (possibly snapped to a grid).
Right now, icons have to be aligned in rows anchored in the top left corner, so that whenever you insert a new one, all the ones after that get pushed right or down, messing up your entire layout.
We've had this ability on desktops since Windows 3 thirty years ago, and Android has had it since day one. As does macOS. Why not iOS?
Why do your icons move around so much? I've added or removed applications from my iPhone and the only limitation I see is that they have to be in a grid with no empty spaces between them. Otherwise the same application icons are in the same place, every day, year after year.
Do you have a screen shot that could illustrate what it is you want to be able to do?
To answer your question: No, I do not, ever. I don't want shit all over my desktop. I have them auto-arranged in a grid. On Windows they start on the left, on Mac they start on the right. So when I (for example) take a screen shot and it gets deposited on the desktop, I know where it's going to be.
But now that you finally gave a concrete example of what you want to do, I can at least picture it.
Yes, this is a very real downside, but Apple has put effort into making the home screen more customizable than it was. It has an app drawer, it has the ability to add/remove home screens without filling one up first, and it has widgets, the major omissions that Android hasn't been missing for many years.
And, yes, it would be really nice if Apple had a system to install third-party launchers, there's no denying that.
I know this is really silly, but you can definitely workaround the issue and effectively have the same end result as Android if you really want it:
Overall, every individual omission from one platform to another is going to be a question of what is important to the buyer.
For some, it might seem ridiculous that, in fifteen years, Apple still doesn't offer a truly customizable home screen. That's a fair criticism. At the same time, it's a fair criticism that it took until 2021 for Google to release a phone that will get 5 years of security and feature updates (Apple never guaranteed this directly, but the iPhone 6S delivered that level of support from when it launched in 2015 until the release of iOS 16 this fall that will drop iPhone 6S support: 7 years of full feature and security updates).
Meanwhile, if you bought a Pixel 3 in 2018, you got your final update this year. I personally think that's downright unacceptable considering the maturity of smartphones when it was released.
The problem with me making comparisons like this is that they'll always seem like a cheap whataboutism, but that's generally how these feature-to-feature comparisons work. For me, in 2016, I saw a situation where Google was not delivering everything I needed in a smartphone, but I also recognize that other people have other needs.
It's not just for cosmetic reasons, there are practical, actual benefits from a user experience standpoint.
For example, I put the apps that I use the most often on the right hand side of the screen, where my thumb can reach them faster. I can't do that on iOS (well, I can, but then any new app I put on the home screen will mess the entire arrangement and I will spend another ten minutes calculating what to insert and where to get all these icons back on the right side of the screen).
I just don't understand how Apple, a company that prides itself on great user experience, is still putting their users through this UX hell fifteen years after the release of the iPhone, and they don't seem to think it's an important feature to add.
> iOS lacks many features that have been standard on Android for years and the only reason it feels so smooth is because the UI thread has pretty much the highest QoL that anything can ever have. iOS would rather drop your network call than drop a single frame.
This is a bit of a simplification but in broad strokes it is kind of correct. And it turns out this actually makes good UI!
You must be kidding. There's no excuse for Android's incompetent architecture, which orphans millions of devices with every release because it apparently lacks a competent hardware-abstraction layer and driver model.
You can install creaky old Windows on millions of devices with disparate hardware configurations on the day of its release, but Android users must wait weeks, months, or forever for their telcos to dribble out hacked, proprietary versions of Android for every model of device ONE AT A TIME. Seriously, WTF? And this is from the great "open-source" OS that was supposed to free us all from vendor and telco tyranny.
Welcome to the wonderful world of ARM and driver blobs. Half of the waiting time is waiting for Qualcomm to release a blob (and that's if they even want to), the other half is including it in your build, and eventually making your fork's changes if you want to do so. For every single SoC in your lineup. Then testing if they can support the new requirements of Android.
Apple would have the same problem if iOS was open source and distributable by anyone, their chips being able to be made by anyone. Once again, Apple has picked the easiest (and least open) path, so, yeah, they can upgrade easily.
Thanks for the info. Why can't the driver be abstracted enough to allow a new OS install as long as the ABI of the driver doesn't change? Major Windows versions installed over the same drivers for years. I've never written a hardware driver, so I'm left to guess or speculate.
No, because generally very few/no people want to install a totally untested OS onto their phone. But the work needed by phone makers to update to a new Android is drastically reduced, so they can reduce the latency by a lot.
Yeah, android is lightyears ahead in a few things, but hardware and privacy-wise iphones are simply that much better. I try to reevaluate the platform every now and then, but the closest I got to changing was Pixel 6 with Graphene - which I decided against due to frequent hardware bugs..
The need for low latency audio on your phone is... debatable.
Power efficiency, absolutely, and a lot of this is due to them not really giving a damn for a while. Which was great! You truly could do anything with your phone, run things in the background forever, etc. Nowadays, Doze, Android Resource Economy and the need to go through Foreground Services/WorkManager makes it quite a bit harder to do.
> The need for low latency audio on your phone is... debatable.
No, it's just not important to you.
Garageband seems to be pretty popular on all the iOS form factors. iOS has for most of its life had a strong offering of music composition and production apps. iOS has had a high quality media framework for years, Android has not.
And if the need is so questionable, why did Android finally get around to addressing it?
And this seems like an odd argumentative path for an Android fan to go down - downplaying the importance of more niche needs outside social media and cow clicking as not important. iOS does just as well or better for messaging, Instagram and TikTok. If you only care about the smart phone basics for the masses iOS ecosystem is pretty hard to beat with better battery life and support.
Android variants all have things that iOS can only dream of having in five years (notifications was a fun one), just spread very unevenly throughout manufacturers. Samsung currently has a very good Android build.
Calling it the best is very far fetched.