mobile-state-model

When to use

• Before implementing async, form, permission, payment, sync, or account-dependent UI.
• When reviewing a screen that handles loading, empty data, errors, offline use, or blocked access.
• When state ownership between UI and business logic is unclear.

Core analysis model

• Enumerate initial, loading, success, empty, partial, error, offline, disabled, submitting, completed, and blocked states.
• Add denied permission, stale data, deleted resource, and session-expired states when relevant.
• Define visible UI, enabled actions, side effects, and recovery path per state.
• Decide which state belongs in UI, view model/controller, cache, navigation, or domain layer.
• Prevent impossible state combinations.

Required outputs

• State matrix.
• State-specific UI behavior.
• Allowed actions per state.
• Retry or recovery path.
• Ownership of state between UI and business logic.