Prepare Android interview answers on lifecycle ownership, ViewModel, process recreation, data layers and offline behavior with a draft-form scenario. These original practice questions connect a concept to a decision and a failure case. They are preparation exercises, not leaked employer questions. State your assumptions before proposing an implementation.
Why does lifecycle ownership matter?
Screens and their associated objects can be created and destroyed as the user navigates or the system manages resources. Identify who owns ongoing work and state. A callback tied to an obsolete screen can waste resources or show the wrong result. Explain what should happen when the screen is no longer active instead of assuming that every operation runs until the user explicitly closes the app.
What does a ViewModel help preserve?
It holds screen-related state and logic across supported configuration changes within its lifecycle. It should not be described as permanent storage for every possible app restart. Process recreation needs an appropriate restoration strategy. Explain which state can be reloaded, which should be restored and which belongs in durable storage. Avoid retaining UI objects with lifetimes shorter than the state owner.
How should the UI and data layer interact?
Present a clear state from the data or domain boundary rather than letting the screen coordinate every transport and storage detail. A repository can express where data comes from, while the screen represents loading, content and failure. Explain who resolves conflicting local and remote values. An abstraction is useful only if its responsibilities and behavior are clear enough to test.
What does offline support require?
Define which operations remain available without connectivity and how the user learns their status. Reading cached content differs from queuing an action to be sent later. Store enough information to retry safely and prevent repeated actions from producing duplicates. Explain how stale content is labeled and how synchronization conflicts are handled. A network-failure catch block alone is not an offline strategy.
How do you test state restoration?
Test the actual transitions the product must support: configuration changes, navigation and process recreation where applicable. Verify that a draft is retained or discarded according to the contract and that work is not started twice unnecessarily. Separate temporary view state from durable business data. Include a test in which the restored screen reloads data that has changed remotely since the original session.
Worked interview scenario
Original case: a user enters a shipping form, rotates the device and later returns after the app process was recreated. Keeping a field only in a view loses it on recreation; keeping it in a ViewModel alone does not establish survival across process death.
Classify each field by sensitivity and persistence requirement. Restore appropriate transient state and store durable drafts where the product requires them. If the user submits while offline, show whether the form is queued, failed or saved as a draft. Test a retry after reconnecting and ensure the same logical submission does not create multiple orders. Explain the chosen lifecycle without promising that every object remains alive forever.
Practice exercise
Create a state table for editing, saving, queued and confirmed states. Explain the owner of each state and the expected outcome after rotation and process recreation. Rehearse a follow-up about clearing a canceled draft and protecting a queued submission from duplicate delivery.
Review your explanation
Use Cluegent during practice to challenge your own draft. Ask for a follow-up about the scenario's weakest assumption, answer it without suggestions, then check your reasoning against the official reference. Review current plans before subscribing. Follow the employer's tool policy in the actual interview.
Sources checked
These official references support the guide. Product details and technical documentation can change; check the linked source for current information.
Where Cluegent helps
Cluegent supports permitted live workflows with transcript context, typed prompts, screenshot-aware answers, resume context, custom response behavior, quick action buttons, and a private desktop overlay. It is most useful when you already understand the subject and need help staying structured under pressure.
Frequently asked questions
Does ViewModel permanently store data?
No. Define restoration and persistence separately for process recreation and durable business records.
Does cached content mean the app supports offline writes?
No. Offline writes need an explicit queue, status, synchronization and duplicate-handling strategy.