Mobile Architecture: Platform Strategy, Patterns & Release Management

Generic, brand-neutral engineering capability; sourced playbooks in references//knowledge/. [DOC]

TL;DR

Mobile architecture defines how mobile applications are structured, how they communicate with backends, handle offline scenarios, manage state, and reach users through app stores. This skill produces comprehensive mobile architecture documentation covering platform selection, app architecture patterns, offline-first design, performance optimization, backend integration, and release strategy [EXPLICIT]

When to Use

• Choosing between native, cross-platform, or hybrid mobile development
• Designing app architecture (MVVM, MVI, Clean Architecture, modularization)
• Implementing offline-first data synchronization
• Optimizing mobile performance (cold start, memory, battery)
• Designing backend APIs specifically for mobile consumption
• Planning mobile CI/CD, code signing, and app store distribution

When NOT to Use

• Backend service architecture --> use software-architecture skill
• API design without mobile-specific concerns --> use solutions-architecture skill
• Assessing existing mobile app health --> use mobile-assessment skill
• UX content and microcopy --> use ux-writing skill

---

Sub-capabilities (resource map)

Deep, evidence-tagged playbooks — open the one the task needs (ICM Layer 3, on-demand). [INFERENCE]

Procedure

1. Resolve the sub-capability; open the matching references/ playbook. [EXPLICIT]
2. Apply its decision tables; pick the strategy explicitly. [EXPLICIT]
3. Validate against the Quality Criteria and tag every claim. [EXPLICIT]

Quality Criteria

• Sub-capability resolved to one playbook. [INFERENCE]
• Claims evidence-tagged. [EXPLICIT]

Contract

• Aceptación: capability resolved to its reference playbook, applied, validated, evidence-tagged. [EXPLICIT]
• Límites: · Does not design backend services (use software-architecture skill) · Does not assess existing app health (use mobile-assessment skill) · Does not cover API design in isolation (u. [EXPLICIT]
• Casos borde: Caso Estrategia de Manejo --- --- Desarrollador unico construyendo para ambas plataformas (iOS + Android) Cross-platform obligatorio (Flutter o React Native). Maximizar. [EXPLICIT]
• Supuestos: · Target platforms defined (iOS, Android, or both) · Minimum OS version requirements established · Backend API exists or is being co-designed · Team skills assessed for platform de. [SUPUESTO]
• Trade-off: Decision Enables Constrains When to Use --- --- --- --- Native Best performance, full API access 2x codebase, 2x team Performance-critical, platform-specific . [EXPLICIT]

Packet

Capas del packet, cargables bajo demanda (disciplina ICM: una capa por vez, nunca todas juntas): references/ guías de profundidad (cargar UNA por etapa) · knowledge/ cuerpo de conocimiento · prompts/ prompts listos · examples/ salida de ejemplo · agents/ subagentes del packet · assets/ recursos estáticos.