19 ms·

Ohh, so that's why entering the passcode on my ipad feels so wonky. I guess this is some kind of legacy thing because the first iphone wouldn't have been able

Ohh, so that's why entering the passcode on my ipad feels so wonky. I guess this is some kind of legacy thing because the first iphone wouldn't have been able to handle it? Because this seems like an exceptionally bad decision, unless absolutely necessary for some reason.

ricardobayes 5y ago
Must be deep-rooted like the UI render refresh issue on Android. No matter how fast the hardware of an android phone, it will always will be a bit clunky/laggy. "Android has a difficult time dealing with the touch interface because it handles rendering "on the main thread with normal priority," as opposed to iOS, which treats UI rendering with real-time priority." https://appleinsider.com/articles/11/12/07/former_google_intern_explains_why_ui_lag_occurs_more_often_in_android_than_ios https://appleinsider.com/articles/11/12/07/former_google_int... Also try endlessly scrolling your photos on your iphone and on an android device - the difference in memory management will be apparent.
- drusepth 5y ago
  No matter how fast I type 3 + 6 + 9 into the stock Android calculator (on a Pixel 3a, 2 years old), I can't replicate keypresses getting ignored or laggy, input-blocking animations. There's also zero lag scrolling through Google Photos. I don't have an iPhone to compare to, but I can't imagine how it could get any better. If this is actually still a problem 10 years after the linked article was posted, I'd say the main problem is then instead the variety of processing in Android devices. I'd guess I'd see these issues on cheaper phones (maybe I can dig up one of my $79 burners to try with), but I doubt this problem exists on any phones of comparable pricing to iPhones. Comparing iOS to "Android" might show some clunky/laggy UI in cheaper models, but comparing iOS to iPhone-priced Android phones most certainly won't (most of the time). [*]: Though, obviously, I expect the sheer amount of variety in Android phones to still produce some expensive, low-power phones that would be an exception here.

ricardobayes 5y ago

Must be deep-rooted like the UI render refresh issue on Android. No matter how fast the hardware of an android phone, it will always will be a bit clunky/laggy. "Android has a difficult time dealing with the touch interface because it handles rendering "on the main thread with normal priority," as opposed to iOS, which treats UI rendering with real-time priority." https://appleinsider.com/articles/11/12/07/former_google_intern_explains_why_ui_lag_occurs_more_often_in_android_than_ios https://appleinsider.com/articles/11/12/07/former_google_int... Also try endlessly scrolling your photos on your iphone and on an android device - the difference in memory management will be apparent.

drusepth 5y ago
No matter how fast I type 3 + 6 + 9 into the stock Android calculator (on a Pixel 3a, 2 years old), I can't replicate keypresses getting ignored or laggy, input-blocking animations. There's also zero lag scrolling through Google Photos. I don't have an iPhone to compare to, but I can't imagine how it could get any better. If this is actually still a problem 10 years after the linked article was posted, I'd say the main problem is then instead the variety of processing in Android devices. I'd guess I'd see these issues on cheaper phones (maybe I can dig up one of my $79 burners to try with), but I doubt this problem exists on any phones of comparable pricing to iPhones. Comparing iOS to "Android" might show some clunky/laggy UI in cheaper models, but comparing iOS to iPhone-priced Android phones most certainly won't (most of the time). [*]: Though, obviously, I expect the sheer amount of variety in Android phones to still produce some expensive, low-power phones that would be an exception here.