Cloud and infrastructure
Hosting, deployment pipelines, backups and monitoring, set up so releases are routine rather than risky.
Learn moreServices
We build iOS and Android applications for customer-facing products and for the teams that run them, and we stay with the app through the parts most people underestimate: store review, releases, and every version after the first one.
Two kinds of app, usually. One is for your customers: booking, ordering, accounts, notifications. The other is for your own people in the field, capturing information away from a desk and often on a patchy connection. They look different but they share a backend, and getting that shared layer right is most of the work.
We have shipped this ourselves. Gashtiq, one of our three products, is a bus booking platform, so we have lived with the parts that only appear in production: a release that has to go out on a Friday, a customer on an old phone, a payment that has to be traceable a month later.
Businesses whose customers expect an app rather than a website, operations teams working away from an office, and companies that already have a web product and now need it in a pocket. If a mobile-friendly website would do the job, we will say so. An app is a bigger commitment and it should be the right one.
The same three steps on every project, whatever the service.
A short brief or one call. No forms, no sales process.
You get a written plan and a fixed price within 24 hours.
You review at every stage. Deployed, documented and handed over.
App projects get a scope naming the platforms, the screens and the store accounts involved, because an unclear answer to any of those three is where app budgets go wrong.
We build cross-platform from one codebase rather than writing the same app twice, and we choose the framework per project rather than defaulting to one: the right answer differs for an offline-first field tool and a content-heavy consumer app. Backends use the same TypeScript, Postgres and managed cloud tooling as our web work, so a product with both a site and an app shares one source of truth instead of two that drift apart.
Projects rarely stop at one service. These two come up most often alongside this one.
Hosting, deployment pipelines, backups and monitoring, set up so releases are routine rather than risky.
Learn moreVisual identity, design systems and content structure so everything you publish looks like it came from one company.
Learn moreSend a short description of what you need. You will have a reply within 24 hours, and a fixed scope and quote once we understand it.