A screen that survives rotation is not necessarily safe from process death. A ViewModel keeps state through configuration changes, but Android can kill a background process to reclaim memory. When the user returns, a new ViewModel is created, and any form values or edits stored only in the old one are gone. Testing rotation alone can therefore hide an important state-restoration failure. Use the storage that matches the data: rememberSaveable for small UI state, SavedStateHandle for small values needed to rebuild a screen, and a database, DataStore, or backend for important or lasting data. For an edit screen, saving an orderId and loading the latest order is often better than saving the full object in SavedStateHandle. Test the real scenario by backgrounding the app, killing its process, and reopening it from Recent Apps to confirm that the screen can rebuild itself.