3 ms·

You could disable animations on iOS through accessibility options. As a rule a flagship iPhone is at least 30% faster than flagship Android (by which I basicall

by ein0p 2y ago

You could disable animations on iOS through accessibility options. As a rule a flagship iPhone is at least 30% faster than flagship Android (by which I basically mean Samsung Galaxy) on realistic workloads.

diggan 2y ago
> You could disable animations on iOS through accessibility options No, you cannot (mentioned here: https://news.ycombinator.com/item?id=41409580 https://news.ycombinator.com/item?id=41409580). Makes it even worse in the cases I tested actually. > As a rule a flagship iPhone is at least 30% faster than flagship Android (by which I basically mean Samsung Galaxy) on realistic workloads. That's cool, but not what I'm talking about. Even my Motorola Moto G4 (released in 2016) allowed me to turn off the animations, so even that one "appears" faster than my iPhone 12 Mini only because iOS forces you to wait for animations to finish.
Dylan16807 2y ago
A phone doesn't spend much time doing "workloads". UI animations in particular should never be close to CPU or GPU bound.
- ein0p 2y ago
  And they aren’t. The op probably just didn’t like some hyperparameter, like duration, because it had a different value than on Android.
  - Dylan16807 2y ago
    Yes, I agree, that is what they meant by slow animations. So why did you bring up compute power? They specifically said "not because poor performance". Also I don't think "just" is the word to use here. Slow is slow, and when it's on purpose it's harder to avoid.
    - ein0p 2y ago
      Slow is in the eye of the beholder. Of all the legitimate complaints one could make about Apple, “slow” is somewhere towards the bottom of the list.
      - Dylan16807 2y ago
        The threshold of what is too slow is in the eye of the beholder, but there have been good studies done on that topic and small delays do cause problems. But the general idea of things being slowed down by animations is objective. It could be done in a frame or two, it takes X frames. And you can add up those delays when you're navigating and reach significant numbers.

by ein0p 2y ago

diggan 2y ago

> You could disable animations on iOS through accessibility options No, you cannot (mentioned here: https://news.ycombinator.com/item?id=41409580 https://news.ycombinator.com/item?id=41409580). Makes it even worse in the cases I tested actually. > As a rule a flagship iPhone is at least 30% faster than flagship Android (by which I basically mean Samsung Galaxy) on realistic workloads. That's cool, but not what I'm talking about. Even my Motorola Moto G4 (released in 2016) allowed me to turn off the animations, so even that one "appears" faster than my iPhone 12 Mini only because iOS forces you to wait for animations to finish.

Dylan16807 2y ago

A phone doesn't spend much time doing "workloads". UI animations in particular should never be close to CPU or GPU bound.

ein0p 2y ago
And they aren’t. The op probably just didn’t like some hyperparameter, like duration, because it had a different value than on Android.
- Dylan16807 2y ago
  Yes, I agree, that is what they meant by slow animations. So why did you bring up compute power? They specifically said "not because poor performance". Also I don't think "just" is the word to use here. Slow is slow, and when it's on purpose it's harder to avoid.
  - ein0p 2y ago
    Slow is in the eye of the beholder. Of all the legitimate complaints one could make about Apple, “slow” is somewhere towards the bottom of the list.
    - Dylan16807 2y ago
      The threshold of what is too slow is in the eye of the beholder, but there have been good studies done on that topic and small delays do cause problems. But the general idea of things being slowed down by animations is objective. It could be done in a frame or two, it takes X frames. And you can add up those delays when you're navigating and reach significant numbers.