How we work
A clear sequence from the first conversation to a published app, with something you can hold in your hand at every stage.
Discovery call
A conversation about what the app should do, who it is for and what already exists. No preparation needed on your side.
Proposal
A written scope with the platforms, technologies, milestones and price for your project, based on what we learned in the call.
Design and prototype
User flows and a clickable prototype you can try on your phone before development begins.
Build in iterations
Short cycles, each ending with a working build you can install and give feedback on.
Testing and release
Automated and device testing, store preparation, submission and a staged rollout.
Support
Updates for new platform requirements, fixes and new features, on terms agreed in advance.
What you can expect from us
- One named contact who knows your project
- Working builds instead of status slides
- Code in your repository from the first commit
- Written decisions, so nothing depends on memory
- Honest advice when a simpler option would do
Questions about the process
How do you estimate a project?
After the discovery call we write a proposal that breaks the work into milestones. Each milestone has a defined scope and price, so there are no open-ended budgets.
How often will we see progress?
At the end of every iteration you receive a build to install on your own phone, together with a short written summary of what changed.
Who owns the code and accounts?
Source code is kept in a repository you control, and apps are published from store accounts in your company's name. Ownership terms are set out in our terms of business.
Can we start small?
Yes. Many clients begin with an audit, a prototype or one platform before committing to a larger build.