4 ms·
It seems tailored for specific use cases and the various scenarios it handles seem to me to have been addressed well. Is it the particular scenarios that you fe
by glhaynes 16y ago
It seems tailored for specific use cases and the various scenarios it handles seem to me to have been addressed well. Is it the particular scenarios that you feel aren't sufficiently well handled or is it that there are scenarios that aren't handled at all? (I'm sure there are some scenarios that aren't handled at all, but I haven't thought of any that would be glaringly missing in the vast majority of people's usage.)
Also, I'm curious what about the app switching is more poorly implemented than Android's version of the same?
- usaar333 16y agoThat apps are killed slows it down. On Android it takes just over half a second to switch applications. For apps that start fast (notepad), this is no big deal. But for things like the browser or skype, it is. It takes 4 seconds for him to switch back to swype: http://www.youtube.com/watch?v=ThkbDcZ_9-k#t=2m30s http://www.youtube.com/watch?v=ThkbDcZ_9-k#t=2m30s This is also seen when switching to the browser near the end of Techcrunch's video: http://www.mobilecrunch.com/2010/04/08/first-video-of-iphone-multitasking/ http://www.mobilecrunch.com/2010/04/08/first-video-of-iphone...
- glhaynes 16y agoI've wondered why iOS kills the last app when it switches away... is it that iOS devices are more memory constrained? Is it that they don't want to disrupt the foreground app by collecting that memory when it's needed rather than immediately? Is it that they want app developers to be more careful about being able to reopen to the same spot they were, perhaps so that the experience of opening the app isn't different depending on whether the app got terminated while in the background or not (or even between device boots)?