Design for the moment the phone is needed.
Create mobile experiences shaped around the user’s environment, device and connection, from employee tools to customer and field applications.
What this covers.
Applications for phones and tablets where the device, the connection and the environment are part of the requirement: offline behaviour, background sync, notifications, camera and scanning, and the store submission process at the end of it.
How it runs.
The offline and sync model is designed first, because retrofitting it is a rewrite. Builds go to your testers on real devices early. Store listings, provisioning and release process are handled as part of delivery rather than discovered in the final week.
Where it fits.
Where people work away from a desk, or where the device does something a browser cannot. If a responsive web application would serve, that is usually cheaper to build and much cheaper to keep current.
What you get, and what it depends on.
An application on both platforms with its offline behaviour designed rather than retrofitted, plus the store listings and release process. It depends on early access to real devices in the environment they will be used in.
How we can work together
The model is chosen to suit the work, not to suit us. We will tell you when a fixed price is the wrong instrument.
App delivery
Design through store release, on iOS and Android.
Companion app
A mobile surface added to a system that already exists.
Release management
Ongoing builds, store submissions and platform version upkeep.
What would a better working day look like?
Bring us the process you want to improve. We’ll explore the product, technology and delivery work it needs.