Design a mobile application around lifecycle, navigation, state ownership, native boundaries, offline behavior, background execution, and platform conventions.
Installs into .claude/skills of the current project.
Are you the author of Mobile App Architecture?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/dadmin88-mobile-app-architecture)
---
name: mobile-app-architecture
description: Design a mobile application around lifecycle, navigation, state ownership, native boundaries, offline behavior, background execution, and platform conventions.
---
# Mobile App Architecture
Use when this procedure is the primary professional method needed for the assignment.
## Procedure
1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using product flows, target platforms/versions, API contracts, native features, offline needs, and performance constraints. Do not fill material gaps with assumptions when they can change the result.
3. Map foreground/background/terminated states, define navigation/state persistence, isolate native capabilities, design sync authority, and account for OS resource constraints.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.
## Quality gate
Critical workflows survive expected lifecycle transitions without duplicate work, stale state, or platform-inappropriate behavior.
