3 ms·

iOS's UI/UX is far more responsive and consistent in reaction times and input latency than Android. I suspect Android's use of Java to be the main culprit, but

iOS's UI/UX is far more responsive and consistent in reaction times and input latency than Android. I suspect Android's use of Java to be the main culprit, but not really sure on that... For browsing, it means that even phones which perform better in CPU bound benchmarks than my old iPhone 11 have random UI stutters & non-smooth scrolling in browser mostly while content is still loading, and these make me miss-click somewhere where I didn't want to, frequently enough to notice (compared to iPhones where it rarely happens)... 120Hz displays on Android make the UI smoother, but random janks & stutters still happen a lot more than on iPhones... When I'm taking photos most of the time I want to take a good picture as fast as possible, sometimes I want to take more in quick succession, this is also somehow easier on iPhones from my experience.. (although I admit it's been a long time since I held a top-tier Android phone, my only contact with Androids is with my friends & family phones which are mostly Xiaomi/Huawei/OnePlus priced around 300-400€ which is half the price of my iPhone) Also, switching to a newer iPhone is seamless compared to buying a new Android, and UI/UX/Settings don't change much with new versions, compared to Android version updates (although from what I've heard this has gotten better in Androids recently) In your analogy I'd be talking about a power drill that just makes me work faster because it's better designed and more intuitive to use, even though it might have less RPM and less bits support.., if I did a lot of drilling just on Philips and Flathead and it saved me enough time, it would be worth the saved time I can use for other stuff...

BoorishBears 4y ago
This right here is it for me. I was the same, in high school there was a 50/50 chance if on a given day the rom I had installed could actually make phone calls, but I didn't mind... but obviously priority change over time. Switching the iPhone I was struck by how damn smooth everything was. Years of XDA tweaks couldn't touch my iPhone 6 out of the box despite specs I had always seen as inferior. My tongue in cheek saying will always be: I'll switch back to Android when you can rotate an app correctly. For those not familiar with Android internals, the UI "framework" the OS provides doesn't support that basic use case. Phones are fast enough that it can be hidden with an animation, but unless an app explicitly signs out every view is torn down and redrawn in a new orientation. It's a tiny thing, but to me it's the iconic symptom of Android vs iOS. That's a decision Android made to support devices with 256mb of RAM, but never prioritized improving on, and now Android UX is stuck with that nit for eternity.
- deleted 4y ago
  [deleted]

BoorishBears 4y ago

This right here is it for me. I was the same, in high school there was a 50/50 chance if on a given day the rom I had installed could actually make phone calls, but I didn't mind... but obviously priority change over time. Switching the iPhone I was struck by how damn smooth everything was. Years of XDA tweaks couldn't touch my iPhone 6 out of the box despite specs I had always seen as inferior. My tongue in cheek saying will always be: I'll switch back to Android when you can rotate an app correctly. For those not familiar with Android internals, the UI "framework" the OS provides doesn't support that basic use case. Phones are fast enough that it can be hidden with an animation, but unless an app explicitly signs out every view is torn down and redrawn in a new orientation. It's a tiny thing, but to me it's the iconic symptom of Android vs iOS. That's a decision Android made to support devices with 256mb of RAM, but never prioritized improving on, and now Android UX is stuck with that nit for eternity.

deleted 4y ago
[deleted]