App development
Apps for the App Store and Google Play. Modern stack, fast, robust and ready for market.
An app should either solve a problem people have every day, or give you a channel you do not already have. If it does neither, a website is cheaper and better.
When it does make sense, we build it to last. Not a prototype that has to be rewritten the moment the first real user gets hold of it.
App or website
We ask that in the first meeting. An app is more expensive to build and more expensive to keep alive, so it has to earn its place.
Scoping version one
The fastest route to a bad app is building everything at once. We cut down to what is needed to test the idea on real users.
Technology choice
We pick the stack on what the app has to do and who maintains it afterwards — not on what is most interesting to build.
iOS and Android at once
We build across both platforms from the same codebase, so you are not paying for the same work twice.
Backend and admin
An app is rarely just an app. There usually needs to be somewhere you can edit content, see users and follow what is happening.
Publishing to the stores
We handle the review process at Apple and Google. That is the part that surprises people most, and it goes easier when someone has done it before.
Store approval is the part that wrecks timelines
The app itself is rarely the problem. It is the review process at Apple and Google, where a rejection can cost a week and a fresh submission. We build that into the schedule from the start rather than promising a date and asking for understanding afterwards.
See packages and pricingHow we deliver
The same approach whatever the area. You can stop after each phase, and you know what the next step costs before agreeing to it.
We map it out first
Ninety minutes going through your processes to work out what can genuinely be automated. You get a clear picture of what is possible and what it would cost.
We build on a fixed price
One- to two-week sprints, each ending in a demo. You know the cost before we start, and you own the code afterwards. No lock-in, no long contract.
We keep it running
Service plans covering maintenance, support and extensions as the business changes.
Is this the right place to start?
If two or more of these sound familiar, there is usually something to gain. If none do, we would rather say so now than after a proposal.
- Users need the solution on the move, not at a desk
- You need notifications, camera or offline access
- A website has been tried and does not go far enough
- The app is the product, not an add-on
Questions we get asked
Do we need an app, or is a website enough?+
We ask that ourselves in the first meeting, and we say so honestly when the answer is a website. An app is more expensive to build and more expensive to keep alive, so it has to earn its place.
How long does an app take?+
A first version to test on the market is usually nine to twelve weeks. A finished production app with an admin panel around fourteen to eighteen. We can be more precise once we know what it has to do.
What does it cost to keep running?+
There are fixed costs for developer accounts at Apple and Google, running the backend, and ongoing updates as the operating systems change. That last one is unavoidable — an unmaintained app lasts about eighteen months.
Can you take over an app someone else built?+
Sometimes. It depends entirely on how it is put together. We look at the code first and say honestly whether taking it over or rebuilding is cheaper.