mobile-engineering-handoff

When to use

• After planning a feature and before coding.
• When converting specs or designs into implementation tasks.
• When a screen file risks becoming too large or stateful.

Core analysis model

• Define the screen shell, route parameters, and navigation effects.
• Split sections, primitives, state renderers, and reusable components.
• Assign state ownership to UI, view model/controller, domain service, cache, or navigation.
• Identify events, analytics hooks, side effects, and async boundaries.
• Keep presentation components reusable and business logic centralized.
• Flag framework, platform, accessibility, and performance risks.

Required outputs

• Suggested file structure.
• Component tree.
• State ownership notes.
• Event handling notes.
• Implementation warnings.