Skip to main content

Offer

App development

App development for a product people carry with them. The app does the job, instead of sending them between a scorecard, a map, and a chat.

The product

App development here means the thing in someone's hand: the task, the people, and the data that task needs. It is not a brochure squeezed onto a phone.

How a build runs

You send a note with what you have. The first conversation is about the customer, what is falling short, and what a good outcome looks like. Pages, features, and timeline get written down before any code.

Then a sketch of the structure, the build, a private staging link, feedback, and launch. The same two people stay on it through handover.

An app we have built

Mully is a golf app for a group that wants the round, the map, and the weekend in one place. It has hole-by-hole scoring, a course map with distances, friends and messages, and multi-day events with a live snake draft. There is no public store listing yet. A demo is available on request.

Questions

What should the first screen do?

Show the job the app is for. Mully opens on the round: scoring, the hole, and the people in it.

Is this a phone version of a website?

No. App development here is the product itself. The phone app stays on its own stack, with the course data, accounts, and live updates behind it.

Is there a public store listing?

Not yet. A demo is available on request.

How do we start?

Use the contact page. Tell us what the app has to do and where the work is split across other tools today. We reply with a written scope.

Describe what the app has to do. We'll get in touch to talk through how we'd do it.

Contact us