Decide where the product belongs
We begin with users, core tasks and the conditions in which the application will be used. Device capabilities, connectivity, distribution and existing systems all influence platform choice. A browser product may suit shared access, while a mobile application may need capabilities or delivery routes that justify its additional scope. We identify user roles, important data and the actions that require approval. The product brief prioritises a coherent first release and names what is outside it. This prevents platform decisions from becoming a substitute for deciding which problems the application should actually solve.
Design behaviour and build the data model
Prototypes establish the main flows before development, including empty states, validation and recovery when an operation fails. Engineering planning covers authentication, authorisation, storage and interfaces with external systems. We distinguish data available immediately from operations that take time and need progress feedback. Offline behaviour, synchronisation and device permissions are considered when the use case requires them, rather than promised by default. The implementation is reviewed through regular working demos. Changes to scope are visible decisions, so a useful discovery during development does not quietly become an open-ended feature commitment.
Prepare for release and ownership
Testing focuses on agreed user journeys and important failure paths, with platform-specific checks where needed. Release planning covers environments, account access, configuration and distribution requirements. A mobile store submission is a separate acceptance step from a successful development build; its responsibilities and dependencies must be named. The handover includes code, operating documentation and a record of external services. We agree support and maintenance arrangements explicitly, including how changes to operating systems or dependencies will be handled. Your team should understand what has been verified, what remains environment-dependent and how to continue developing the product.
The release brief names the journeys that must work before launch and the evidence expected for each. This can include account creation, permission changes and recovery from an interrupted task. A clear acceptance list helps distinguish a working demonstration from a product ready for the particular users and environment agreed.