Custom software development
Most businesses run on a spreadsheet that three people understand and nobody trusts. We replace those with something auditable that the whole team can use.
See how we do itMobile apps
Most app projects start with a specific job: automate something manual, give customers or staff mobile access, or take a system that already works and put it in a pocket.
The problem
Our approach
The first question is whether you need an app at all. A responsive website costs less, needs no app store approval, and updates instantly — if that covers the requirement we will say so. An app earns its place when it needs the camera, GPS, offline access, push notifications, or a home-screen icon people tap daily. Once that is settled, we pick cross-platform or native against what the app actually does, rather than out of habit, and we write down why.
Scope
Whether an app is the right answer, and if so, Android, iOS or both, cross-platform or native — with the trade-offs written down.
Screens designed for one-handed use on a phone, not a desktop layout squeezed narrow.
Built to be extended and handed over, with a codebase a future developer can pick up.
The server side the app talks to, whether that is new or an existing system of yours.
Developer accounts, store listings, screenshots, privacy declarations and the review process, through to approval.
Fixes, OS compatibility as Android and iOS move on, and new versions when you need them.
What you get
Built with
The stack follows the requirement. If something else fits better, we will say so.
Questions
Often a responsive website is the better answer — cheaper, no store approval, and updates the moment you publish. An app is worth it when you need the camera, GPS, offline use, push notifications, or something people open every day. We will tell you honestly which one your requirement points to, including when it is the cheaper option.
Often, yes. We start by reading the code and the backend and telling you plainly whether it is worth continuing or cheaper to rebuild. Sometimes the honest answer is rebuild, and we will say so rather than charge you to patch something that will keep breaking.
Cross-platform, usually Flutter, when the app is mostly screens, forms and data — one codebase for both platforms costs less to build and less to maintain. Native when the app leans hard on hardware, background services or platform APIs, or when performance is the product. The requirement decides, not our preference.
Yes. We handle the store listings, screenshots, privacy declarations and the review process, including the rejections that are a normal part of a first submission. The developer accounts stay in your name — an app published under an agency account is a problem the day you want to leave them.
You do, from the first commit. The repository is in your account, not ours, and the store listings are under your developer accounts.
Related
Most businesses run on a spreadsheet that three people understand and nobody trusts. We replace those with something auditable that the whole team can use.
See how we do itWe design and build websites on a custom stack. Fast, editable by your team, hosted wherever you like, and yours to take elsewhere if you ever want to.
See how we do itOrder updates, booking reminders, lead follow-up and AI calling on the official WhatsApp Business API — connected to your website, CRM and payment gateway rather than sitting in a dashboard on its own.
See how we do itNext step
Send a short description. We reply within one business day with an approach, a rough range, and the questions we still need answered.
Scripted, not an AI. Anything you send here reaches the team.