An app idea?
Let’s give it a job.
What should someone be able to do with it? Starting there helps us choose the right first version, whether it runs in a browser or needs native app features.
For a defined product or business task that needs an application and a practical route to a first release.
Be specific about the first user.
Tell me when they would open the app and what they need to finish. We use that journey to decide the initial screens, information and success checks. Extra ideas go into a separate list.
Choose the platform for the task.
A browser app, installable web app and native mobile app have different capabilities and release requirements. Offline use, notifications, camera access and app-store distribution need an explicit decision.
Try a prototype.
We agree what the prototype demonstrates and which parts use sample data. You can test the flow before the production build, with the scope and payment stages clear.
Plan for the app after launch.
Accounts, hosting, updates, provider charges and any app-store responsibilities belong in the proposal. The code and data handover follows the project agreement, including existing tools and third-party licences.
A few things to sort out.
Does the first version need every feature?
No. We agree a useful complete journey for the first release and price additional work separately.
Can it work offline?
That depends on the task, data and platform. We assess offline behaviour, conflict handling and any security requirements before including it in the scope.
Show me the bit
that slows you down.
A task, a spreadsheet or an idea you want to work through. Describe it first and we can agree what to look at next.