7 ms·
I believe the point is that the "main thread" for your iOS application, is not the main thread of the OS. They're totally decoupled.
by ubertoop 5y ago
I believe the point is that the "main thread" for your iOS application, is not the main thread of the OS. They're totally decoupled.
- IAmLiterallyAB 5y agoErr, same with Android? And every OS ever. That's just standard process isolation. Or am I misunderstanding something?
- brianwawok 5y agoThere’s some deep dive articles on the way the input loop works. But OP is correct, and the reason iOS feels smoother. Android has a lot more UI lag.
- codedokode 5y agoI don't think Apple has any special tricks for input loop. Some Android phones really have input lag, but it is not caused by CPU load. For example, on my phone, there is approximately 100-150 ms lag between tapping the screen and registering the touch. The lag is not caused by CPU load, but by slow touch sensor. I don't think Apple has any smart code optimization tricks. Either they have a faster touch sensor or just some people believe that if something is made by Apple then it is of a better quality. Here is a comparison of input lag in games in iOS and Android [1] and it shows similar results: 80 ms between a tap and reaction on screen. [1] https://blog.gamebench.net/touch-latency-benchmarks-iphone-xs-max-galaxy-note-10 https://blog.gamebench.net/touch-latency-benchmarks-iphone-x...
- ajconway 5y agoThey do! See https://devstreaming-cdn.apple.com/videos/wwdc/2015/233l9q8hj9mw/233/233_advanced_touch_input_on_ios.pdf https://devstreaming-cdn.apple.com/videos/wwdc/2015/233l9q8h... and the corresponding WWDC session on them minimizing the input-to-display time.
- taneq 5y ago<laughs in Windows 3.1>