How to scope a software project before you ask for quotes
Vague briefs produce quotes that cannot be compared. A few days of structured thinking before you contact suppliers will save weeks of confusion later.
Service 03
Mobile apps people keep on their home screen
We design and build iOS and Android apps from a single Flutter codebase, along with the backend, notifications and admin tools behind them. The aim is an app that feels at home on both platforms and does not cost twice as much to maintain.
- Outcome
- A dependable app on both platforms, without the cost of maintaining two separate codebases.
- Typical stack
- Flutter, Firebase, Supabase, Node.js, TypeScript, PostgreSQL, Google Cloud
When this is the right call.
Your customers expect an app
Users want to book, order, track or check in from their phone, and a mobile website is no longer enough for how often they come back.
Two native apps cost too much
Maintaining separate iOS and Android codebases means double the work for every feature and bug fix, and the two versions drift apart.
Field teams need mobile tools
Staff on site, on the road or in a warehouse are working from paper, messages or a desktop system squeezed onto a phone screen.
Your existing app is poorly rated
Crashes, slow screens and confusing flows are showing up in reviews. You need someone to stabilise it and set a clear path forward.
What you get.
Cross-platform apps with Flutter
One codebase producing native iOS and Android apps, with platform-appropriate behaviour where it matters to users.
App backends and APIs
Authentication, data storage, file uploads and business logic, built so the app and any web interface share the same foundations.
Push notifications and offline support
Timely, relevant notifications and local data handling so the app keeps working when signal drops.
Admin and content tools
A web-based control panel so your team can manage users, content and orders without a new app release.
App store release and updates
Store listings, review submissions, staged rollouts and a repeatable release process for future updates.
How we approach it.
For most business apps we recommend Flutter. It produces genuinely native builds for iOS and Android from one codebase, which roughly halves the ongoing work of shipping features and fixes. Where an app depends heavily on a specific platform capability, we will assess whether a cross-platform approach is still the right trade-off before committing.
We treat the backend as part of the product, not an afterthought. Decisions about authentication, data sync, offline behaviour and notifications shape the user experience as much as the screens do, so we settle them early. For earlier-stage products, managed services such as Firebase or Supabase can get you to launch quickly; for more complex needs, we build a dedicated API that can also serve web clients.
Testing covers real devices across a range of screen sizes and operating system versions, alongside automated tests on core flows. We set up crash reporting and analytics before launch so issues are visible from day one. App store accounts, signing keys and source code are registered to you, so you keep full control of the app and its listing.
Tools we use for this work.
From first conversation to production.
- DiscoverUnderstand the business, the users and what success looks like.
- DefineRequirements, architecture, scope and a roadmap you can plan around.
- DesignThe product experience, tested before it is expensive to change.
- BuildEngineering in short cycles, with working software to review every sprint.
- LaunchTesting, deployment and making sure it holds up in production.
- EvolveSupport, improvement and scaling once real usage starts.
Where we apply it.
- Startups & Scale-upsMVPs and platforms built to survive growth
- Healthcare & Health TechClinically safe, interoperable software for health and care
- Logistics & Supply ChainTracking, field apps and integrations for moving goods
- Ecommerce & RetailFast storefronts, integrations and retail operations tooling
Common questions.
Should we build native apps or a cross-platform app?
For most business apps, cross-platform with Flutter is the sensible default: one codebase, one team, consistent features on both platforms. Separate native apps can make sense when an app depends heavily on platform-specific hardware or interface conventions. We will recommend one or the other based on what your app actually needs to do.
What drives the cost of a mobile app?
The biggest factors are the number of screens and user journeys, whether you need a new backend or can use an existing one, offline and sync requirements, payments, and integrations with other systems. Design polish and animation also add time. We scope the smallest release that is worth putting in front of users and build from there.
Do you handle App Store and Google Play submission?
Yes. We prepare builds, store listings and privacy declarations, submit for review and handle any follow-up from Apple or Google. The developer accounts are held by you, so the app remains yours.
What happens after the app launches?
Apps need regular maintenance: operating system updates, new device sizes, dependency upgrades and store policy changes. We offer ongoing support covering these alongside new features, or we hand over to your team with documentation and a working release pipeline.
Can the app share a backend with our website?
Usually, yes, and it is often the better design. A shared API means business rules live in one place, so the app and the website stay consistent and changes only need to be made once.
Often paired with.
- UI/UX & Product DesignUser research, prototyping, interface design and design systems for web and mobile products.
- APIs & IntegrationsCustom APIs and system integrations that connect CRMs, ERPs, payment providers and internal tools.
- SaaS DevelopmentMulti-tenant SaaS platforms with subscriptions, team accounts and an architecture that grows with your customer base.
Have a product worth building?
Tell us what you are trying to achieve. The first conversation is about understanding the problem — not selling you a solution.