2 ms·
I don't know how iOS handles it, but Android treats rotation... oddly. If you haven't specifically handled it, it basically kills your activity, loads the new r
by ydant 15y ago
I don't know how iOS handles it, but Android treats rotation... oddly. If you haven't specifically handled it, it basically kills your activity, loads the new rotated layout (which can be radically different from the other orientation's view), and then reloads your activity. Any initialization, etc, happens again (which is why, sometimes in some apps, you rotate and form fields are cleared).
You can cache data and make rotates pretty seamless, but it still seems like a decent amount of overhead that wouldn't necessarily be there.
- dpritchett 15y agoWhat I saw was even worse... Nook just doesn't even try to rotate most of the time. In iOS the default seems to be that any and every app will rotate in a meaningful way when I turn the device. Not so in my 5 minute demo of the Nook. It's not that it can't smoothly rotate the screen when it wants to, it's that it doesn't attempt to rotate the screen to match my position as often as iOS apps do.
- allwein 15y ago>it doesn't attempt to rotate the screen to match my position as often as iOS apps do It was your particular phrasing of this issue that made me think that this may be a feature of the Nook, and not a bug. My biggest complaint about any iOS device used to be that when I was reading in bed, sometimes I would lie on my side, causing the screen to rotate when I didn't really want it to. Obviously, the screen-orientation lock functionality was a godsend for fixing this issue for me. It occurs to me that maybe, since the "primary" function of the Nook is reading, that it doesn't attempt screen rotation unless it really thinks that was your intent.