I'm considering to build my first iOS app in the following months. This is going to a hybrid app:
At this point is fully migrated to Android and Windows 10. However, one of my greatest challenges in Android was the screen rotation:
- Why the android activity get's destroyed on rotation?
- What is the advantage of letting an activity be destroyed on rotation?
This situation was quite complex to handle since each time my app was rotated the activity was destroyed and I needed to add several workarounds in order to keep the app running, restoring the previous states, colors, stop the timers before the rotation because they kept running in background, etc.
I didn't experience anything similar in Windows 10 and I'd like to know if the iOS View Life-Cycle behaves closely, are the views destroyed during the rotation of any device? Because my workarounds are reusable, but they add certain complexity and reduce performance.
These are some of the sites that I read:
- iOS View Controller Life Cycle
- View Controller Lifecycle iOS applications
- iOS > Android: View Life Cycle
Nevertheless, I haven't found anything precise about this topic.
- I'd like to find if there is any documentation or examples since I invested a considerable amount of time in the Android Specific Situation to avoid finding in the last minute that I needed to reuse the workarounds.
- I'm not sure if this question should be here or in Software Engineering. If I should move it just let me know and I'm going to do it.