Apps

When it fits

An app needs one job that matters to the person holding it. Booking a service, repeating an order or opening a membership are better starts than a long list of features.

The first decision is what people need to do. A customer portal, a web app and a mobile app each solve a different part of that. Which one fits depends on how it gets used, how it reaches people and what the business can run.

What can be in scope

Customer experiences

Booking, ordering, membership and service, put in your customer's hand.

Portals and working spaces

One clear place for customers, partners or your team to find what they need and get work done.

A product from an idea

We work through the offer, the journey and the technical choices with you, then build and test the first release.

What to bring

The person using it

Their situation, what they are trying to do and where the current way lets them down.

The essential journey

The smallest complete task the app has to handle. Everything else can come later.

The business behind it

How the service is delivered, who supports the people using it and which of your systems the app relies on.

Decisions worth making early

The first release

One thing a person can finish from start to end beats ten features left half done.

Accounts and information

Whether people need an account, what you have to know about them and which actions need a second check.

Distribution and upkeep

App stores, device support, notifications and ongoing changes all move the scope. We settle them before choosing how to build.

How we check the work

We walk the whole journey, including the empty screens, the errors and the second visit, and we put it in front of the people it is for when we can. Shipping an app and finding demand for it are two jobs. We plan for both.

The app is one part of the business. We can plan the backend, the launch website, the marketing and the running of it together, so they do not become four projects with four sets of assumptions.