4 ms·
The thing is that the button always works reliably while all their interface swipes are laggy and become unusable under heavy load, in battery saving mode and a
by orloffm 9y ago
The thing is that the button always works reliably while all their interface swipes are laggy and become unusable under heavy load, in battery saving mode and as usual, in a few years after they stop optimizing for the old hardware.
- TekMol 9y agoBut isn't that an implementation detail? I would assume that if they want, they can assign a non-changeable interrupt to the swipe recommendation call.
- otoburb 9y agoThe swipe needs to be recognized as such before the prioritization, while a separate home-buttom IRQ feels more immediate and hence "reliable" under most mental models. One could argue that any tactile event would generate an IRQ so it shouldn't matter whether the interrupt handler is from the screen or home button, except that there intuitively seem to be many more branches and CPU cycles required to determine the actual priority/intent of a tactile interrupt versus a smaller set of branches required for the home button.
- walterbell 9y agoAre there comparative latency numbers between SW dock and HW button, as Apple reports for the Pencil?
- jclardy 9y agoThat is still decided on a software level. The home button on my iPhone has become unresponsive before, even being a physical button. As long as the swipe gesture and "open homescreen" actions are given higher priority I don't think that should be an issue.
- dx034 9y agoI'm more worried about swipe recognition. It regularly happens to me that I want to swipe up the control centre and accidentally press a button in the app instead. Esp if screen or my finger are a bit wet. The home button always works.
- limeblack 9y agoI have an iPhone 4(not as my main device) and the home button is not very responsive on the newest OS. Your point is valid but in my experience the device is laggy when you update even when it has a home button.