Your question is Mobile App Lifecycle State Persistence. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
Mobile apps can be interrupted at any time by incoming calls, OS memory pressure, or user actions. A strong engineer should know how to preserve a good user experience when the app is paused, backgrounded, or killed.
Explain how you would handle the lifecycle of a mobile application and save state when it is abruptly sent to the background.
Your answer should cover:
The interviewer expects a practical systems explanation rather than platform-specific trivia. Discuss lifecycle callbacks/events, in-memory vs persistent state, trade-offs around performance and consistency, and common mistakes such as saving too much or relying on background execution guarantees.