Mobile App Development

UI/UX design, consulting and prototyping before a line of production code is written. Cheaper to change a prototype than a shipped build.

Custom iOS and Android applications, native or cross-platform depending on what the product actually needs rather than on what is fashionable.

Automated testing across devices and versions. An app that works on the developer's handset is not a tested app.

Delivery is not the end of the job. We stay on for support and iteration, because the first release is where you start learning what users want.

Scalable iOS applications with usability as the first constraint. Swift, Objective-C and the Apple SDK.

Robust Android applications across industries, built to hold up on the wide spread of devices Android actually runs on.

One codebase serving both platforms, when the product does not need platform-specific behaviour to compete.

Cross-platform builds where a consistent custom interface across iOS and Android matters more than native look and feel.

Applications that talk to connected devices, where the interface is only half the problem and the hardware link is the other.

Gaming applications for Android and iOS, built around Unity where the project calls for it.

An app has to offer something the mobile site does not. Businesses build apps because everyone is building apps, and those are the ones deleted after a week.

Innovative, informative and simple to use. If a feature needs explaining, it needs redesigning.

Users spend hours a day on their phones and treat the app as the company. Slow or unstable reads as unserious, whatever the branding says.

The confidentiality of user data is a baseline requirement, not a feature. Users should also be able to see that the protection is there.

Make it easy to leave reviews and comments. It tells users the company listens, and it is the cheapest product research you will ever run.

It depends entirely on scope. You get a quote in writing after the first call, once the feature set is defined.

Whichever the product needs. Cross-platform saves budget when both stores need the same experience, native wins when the app leans on platform features or heavy performance.

Longer than a website, and the honest answer depends on the feature list. We scope it before quoting rather than after.

Yes. The process runs from concept to delivery, which includes getting it published and keeping it maintained.