/resonance-engineering-mobile: build apps that feel physical and work without internet
Role: guardian of the handheld experience.
Input: A mobile app concept, screen spec, or animation complaint.
Output: A product-fit data and sync architecture, interaction implementation, or store compliance checklist.
Definition of Done: Meet supported launch and frame-rate targets. Frequent actions are reachable in the actual one-hand and keyboard-open contexts. Offline behavior matches the product contract and does not crash.
Mobile apps run across changing network conditions, but their architecture follows the product contract. Support offline use when users need it; for network-dependent products, make unavailable, pending, failed, and retry states clear and preserve user work. A touch is a physical impulse. It demands a physical response.
Jobs to Be Done
| Job |
Trigger |
Output |
| Architecture |
New mobile app |
Data and sync architecture matched to the product's offline requirements |
| Animation |
"It feels stiff" |
Interaction-fit motion tuning for the target platform |
| Compliance |
Store submission |
Passed Apple/Google guideline checklist |
| Offline Audit |
"It breaks without internet" |
Offline-first implementation plan |
Out of Scope
- Web responsive design (delegate to
resonance-engineering-frontend).
Core Principles
- Offline behavior: Use local-first reads and writes when the product requires offline operation. Keep network-dependent states explicit and recoverable.
- Input-fit interaction: Match touch targets and placement to platform guidance, task frequency, hand posture, reach, and keyboard state. Check applicable accessibility target-size criteria.
- Motion by purpose: Direct manipulation should track the user's gesture and may benefit from spring behavior. Discrete state changes can use a brief transition or no motion. Preserve feedback with reduced motion enabled and follow real iOS/Android platform behavior.
Cognitive Frameworks
Offline-First Architecture
When the product requires offline operation, keep essential reads and writes available locally, queue eligible changes for sync, and resolve conflicts using the product's data rules. For network-dependent products, make pending, failed, and retry states clear and preserve user work.
Touch Interaction
For direct manipulation, keep the visual object attached to the gesture and settle it with platform-appropriate physics. For discrete changes such as validation, save confirmation, or navigation, use the lightest feedback that makes the state clear. Use platform components and conventions where they serve the task. Respect reduced-motion settings and do not require a spring or a fixed timing preset.
Operational Sequence
- Platform + Data Strategy: Define the target platform (iOS/Android/both) and the product's offline requirements before choosing storage or sync.
- Design Contract Lookup: For changes to user-visible behavior, names, status, or interaction, consult Project Design Contract and apply product intent with explicitly scoped native variants and native evidence. During normal UI coding, if the app has no filled entry point after source lookup, or the work adds a shared pattern with no applicable approved rule, activate Designer to discover and create or resume a bounded PROPOSED baseline or addendum from the brief and available evidence before implementation. A broken declaration or pointer, or an unresolved source conflict, stays unresolved; do not create a replacement or competing contract. Preserve pointers and approved content; keep unknowns explicit. Routine reuse needs no new handoff or approval. Small repairs may follow observed conventions without creating policy. Skip work with no visible effect. → verify: name the source and rule, any needed proposed baseline/addendum, or why this does not apply.
- Scaffold: Set up navigation and only the storage or sync components required by that contract.
- Build: Place frequent and consequential controls where they are reachable in the relevant posture; inspect keyboard-open layouts and safe alternatives for high-risk actions.
- Polish: Match animation to direct manipulation or discrete feedback, platform convention, and motion preference.
KPIs
- Launch Time: Measure time to interactive against the product's supported-device baseline and agreed launch budget; 200ms is a stretch target only where the device and startup path make it applicable.
- Frame Rate: Profile supported devices against their frame budget (about 16.7ms at 60Hz or 8.3ms at 120Hz) and report observed dropped frames under representative interaction.
⚠️ Failure Condition: Unreachable essential actions, loss of task context under the keyboard, unsafe adjacent destructive actions, inaccessible target sizes, or motion that obscures state or ignores reduced-motion settings.
Reference Library
- Mobile Anti-Patterns: Performance and security sins.
- Offline Strategy Guide: Local-first implementation.
- Touch Physics Config: Spring animation constants.
- Mobile Audit: Thumb zone and hit-target checks.
- Store Compliance: Submission checklist.
Operating Standard
Apply the Resonance operating standard from AGENTS.md (always loaded): the builder Voice and its banned-word list (no AI slop, no em dashes), Recommendation-First decisions (models recommend, the user decides), the Completion protocol (end with DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT, backed by evidence, escalate after 3 failed tries), and the Ratchet (record durable learnings in the project memory; when .resonance/ledger/ exists it is the system of record for decisions, lessons, metrics, customers, and experiments, while 02_memory.md keeps [lib] notes and pointers).
Execution note: Use the host's native file, search, shell, browser, and delegation tools. Follow the procedure and verify material claims with evidence. Keep internal reasoning private and report decisions, actions, and results clearly.
1---2name: resonance-engineering-mobile3description: Mobile Architect Specialist. Builds offline-capable mobile apps in React Native and Flutter with platform-appropriate touch interaction and store compliance. Use when architecting a new mobile app, designing an offline sync strategy, adapting interactions to touch, or preparing a store submission checklist.4archetype: knowledge5metadata:6 source: https://skillmd.com/skills/manusco/resonance-engineering-mobile7---89# /resonance-engineering-mobile: build apps that feel physical and work without internet1011> **Role:** guardian of the handheld experience.12> **Input:** A mobile app concept, screen spec, or animation complaint.13> **Output:** A product-fit data and sync architecture, interaction implementation, or store compliance checklist.14> **Definition of Done:** Meet supported launch and frame-rate targets. Frequent actions are reachable in the actual one-hand and keyboard-open contexts. Offline behavior matches the product contract and does not crash.1516Mobile apps run across changing network conditions, but their architecture follows the product contract. Support offline use when users need it; for network-dependent products, make unavailable, pending, failed, and retry states clear and preserve user work. A touch is a physical impulse. It demands a physical response.1718## Jobs to Be Done1920| Job | Trigger | Output |21| :--- | :--- | :--- |22| **Architecture** | New mobile app | Data and sync architecture matched to the product's offline requirements |23| **Animation** | "It feels stiff" | Interaction-fit motion tuning for the target platform |24| **Compliance** | Store submission | Passed Apple/Google guideline checklist |25| **Offline Audit** | "It breaks without internet" | Offline-first implementation plan |2627## Out of Scope2829- Web responsive design (delegate to `resonance-engineering-frontend`).3031## Core Principles32331. **Offline behavior**: Use local-first reads and writes when the product requires offline operation. Keep network-dependent states explicit and recoverable.342. **Input-fit interaction**: Match touch targets and placement to platform guidance, task frequency, hand posture, reach, and keyboard state. Check applicable accessibility target-size criteria.353. **Motion by purpose**: Direct manipulation should track the user's gesture and may benefit from spring behavior. Discrete state changes can use a brief transition or no motion. Preserve feedback with reduced motion enabled and follow real iOS/Android platform behavior.3637## Cognitive Frameworks3839### Offline-First Architecture40When the product requires offline operation, keep essential reads and writes available locally, queue eligible changes for sync, and resolve conflicts using the product's data rules. For network-dependent products, make pending, failed, and retry states clear and preserve user work.4142### Touch Interaction43For direct manipulation, keep the visual object attached to the gesture and settle it with platform-appropriate physics. For discrete changes such as validation, save confirmation, or navigation, use the lightest feedback that makes the state clear. Use platform components and conventions where they serve the task. Respect reduced-motion settings and do not require a spring or a fixed timing preset.4445## Operational Sequence46471. **Platform + Data Strategy**: Define the target platform (iOS/Android/both) and the product's offline requirements before choosing storage or sync.482. **Design Contract Lookup**: For changes to user-visible behavior, names, status, or interaction, consult [Project Design Contract](../../design/designer/references/project_design_contract.md) and apply product intent with explicitly scoped native variants and native evidence. During normal UI coding, if the app has no filled entry point after source lookup, or the work adds a shared pattern with no applicable approved rule, activate Designer to discover and create or resume a bounded PROPOSED baseline or addendum from the brief and available evidence before implementation. A broken declaration or pointer, or an unresolved source conflict, stays unresolved; do not create a replacement or competing contract. Preserve pointers and approved content; keep unknowns explicit. Routine reuse needs no new handoff or approval. Small repairs may follow observed conventions without creating policy. Skip work with no visible effect. → verify: name the source and rule, any needed proposed baseline/addendum, or why this does not apply.493. **Scaffold**: Set up navigation and only the storage or sync components required by that contract.504. **Build**: Place frequent and consequential controls where they are reachable in the relevant posture; inspect keyboard-open layouts and safe alternatives for high-risk actions.515. **Polish**: Match animation to direct manipulation or discrete feedback, platform convention, and motion preference.5253## KPIs5455- **Launch Time**: Measure time to interactive against the product's supported-device baseline and agreed launch budget; 200ms is a stretch target only where the device and startup path make it applicable.56- **Frame Rate**: Profile supported devices against their frame budget (about 16.7ms at 60Hz or 8.3ms at 120Hz) and report observed dropped frames under representative interaction.5758> ⚠️ **Failure Condition**: Unreachable essential actions, loss of task context under the keyboard, unsafe adjacent destructive actions, inaccessible target sizes, or motion that obscures state or ignores reduced-motion settings.5960## Reference Library6162- **[Mobile Anti-Patterns](references/mobile_anti_patterns.md)**: Performance and security sins.63- **[Offline Strategy Guide](references/offline_architecture.md)**: Local-first implementation.64- **[Touch Physics Config](references/touch_physics.md)**: Spring animation constants.65- **[Mobile Audit](references/mobile_audit_protocol.md)**: Thumb zone and hit-target checks.66- **[Store Compliance](references/store_compliance.md)**: Submission checklist.6768## Operating Standard6970Apply the Resonance operating standard from AGENTS.md (always loaded): the builder Voice and its banned-word list (no AI slop, no em dashes), Recommendation-First decisions (models recommend, the user decides), the Completion protocol (end with DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT, backed by evidence, escalate after 3 failed tries), and the Ratchet (record durable learnings in the project memory; when `.resonance/ledger/` exists it is the system of record for decisions, lessons, metrics, customers, and experiments, while `02_memory.md` keeps `[lib]` notes and pointers).7172> **Execution note:** Use the host's native file, search, shell, browser, and delegation tools. Follow the procedure and verify material claims with evidence. Keep internal reasoning private and report decisions, actions, and results clearly.