The path through a task
What the person came to finish, in an order that makes sense on a phone.
Solutions
Apps for iOS and Android. For the people who use a product every day, for an organization’s own staff, or as the mobile side of a larger system.
The whole app
An app that only looks like an app is a prototype. We design the interface and build the parts it depends on: sign-in, the records behind the screens, and a version you can put in someone’s hand.
What the person came to finish, in an order that makes sense on a phone.
Who the user is, and what that role is allowed to see or change.
The information the screens read and write, including a system we may also be building.
Not a slide of mockups. A build that can be installed and used.
Designed for the hand
Type that can be read without zooming. Controls within reach. A screen that does not ask for ten decisions when two would do. If a tap does not change the outcome, it should not be there.
The same care applies whether the app is for customers or for the people inside an organization. Staff tools get abandoned just as fast when they are clumsy.
When an app is the right shape
An app earns its place when people are away from a desk, the job is frequent, or the phone already holds the camera, the calendar, or the notification.
A responsive website is sometimes the better first version, especially when the audience is occasional. We will say so. The mobile interface can still be part of a website or a larger system.
What it is for
The daily interface of something you offer: check a status, book, read, submit, or continue a task.
Events, resources, and tools for a community or a staff, with roles that match how the group already works.
The same records as the dashboard or the website, reached from a phone instead of a second, separate app.
What they open it to do, and what system, if any, already holds the data. We will tell you whether an app is the right first build.