What problem does it solve? Mobile app changes often break under real device conditions like process death, connectivity loss, permission denial, or background limits. This Skill supplies the engineering decisions needed to handle lifecycle, navigation, offline sync, storage, and release verification for normal Android and iOS application work. ## Core Features & Use Cases - Lifecycle and State Modeling: Defines foreground, background, suspended, and restored states, and separates UI state, durable local state, and server state so work survives process death. - Offline, Network, and Cache Design: Covers connectivity transitions, retries, cache invalidation, idempotent queued work, and version-compatible API contracts during rollout. - Permissions, Security, and Release Verification: Enforces least-privilege permissions, platform-secure storage, validated deep links, and emulator or device testing across the supported OS/build matrix. - Use Case: When adding an offline-first check-in flow to an Android app, use this Skill to define cache conflict handling, background upload recovery, permission denial states, and the exact device tests required before release. ## Quick Start Use the mobile application engineering skill to design the offline sync and lifecycle handling for my Android check-in flow.
