mobile-feature-planning

When to use

• Before building a new mobile feature or major screen flow.
• When a feature touches navigation, async data, permissions, notifications, deep links, or multiple screens.
• When requirements are vague and need implementation-ready structure.

Core analysis model

• Clarify the user goal and business goal.
• Identify entry points: tab, card, search, deep link, notification, onboarding, settings, or external handoff.
• Map the primary flow, alternate paths, interruptions, and resume behavior.
• Cover system interactions: network, cache, auth/session, permissions, notifications, background refresh, analytics.
• Define state coverage before layout details.
• Translate UX decisions into files, components, state owners, and navigation effects.