The difficulty of an app depends on the operating outcome, platforms, integrations, security, compliance, support, and maintenance—not only the number of screens. A prototype and a production product answer different questions.
1. Research and pre-planning
Define the user, problem, business outcome, platforms, revenue model, constraints, and success measure. Review alternatives and decide which capability is actually differentiated.
2. Sketch the journey
Map the primary flow and the recovery states: empty data, validation, offline use, failed payment, cancellation, permissions, support, and account recovery. Wireframes should expose decisions before visual polish hides them.
3. Assess technical feasibility
Inventory data sources, APIs, authentication, payments, notifications, analytics, privacy, accessibility, app-store requirements, performance, and operational ownership. Validate the riskiest dependency first.
4. Prototype and test
Use a prototype to test comprehension and workflow, not to imply production readiness. Record what must be built, bought, or configured and define acceptance tests for the final product.
Plan the second half
Quality assurance, security review, release operations, observability, support tools, updates, and maintenance often determine the durable cost. Choose an internal team, external team, platform, or hybrid approach from the same written scope.