Consumer apps
iOS and Android apps, designed and built end to end by one team, from the first screen to the store listing. This page describes the full service.
Daypost, our own app
Overview
The people who draw the screens write the Swift and the Kotlin. A decision about an empty state or a loading spinner gets made once, by someone who knows what it costs to build, instead of travelling back and forth between a design file and a ticket.
Most of this work is either a first version heading for the stores or a rebuild of an app that shipped and stopped being opened. Both start the same way: one loop that has to feel effortless. Sign in, notifications, offline sync and the store listing all follow from it.
What the service covers
Everything this work
includes, spelled out
Product strategy
and user flows
Before a screen is drawn we agree what the app is for, who will use it every day, and the one loop that has to feel effortless.
Popular under this
- MVP scoping for a first launch
- App redesigns and rebuilds
- User flows and clickable prototypes
- Audits of an app you already have
Interface and
interaction design
Native patterns first, invention where it earns its place. Every state designed, including the empty and broken ones.
Popular under this
- iPhone and iPad interfaces
- Android interfaces
- Watch apps and widgets
- Accessibility passes
Native iOS and
Android engineering
Swift and Kotlin by the people who designed the screens, so nothing is lost in handoff and decisions are made where they are cheapest.
Popular under this
- iPhone and iPad apps in Swift
- Android apps in Kotlin
- Sign in, profiles and accounts
- Offline first data sync
- Push notifications
- In app purchases and subscriptions
Launch, store
and analytics
Store listings, review handling, crash reporting and the analytics that tell you what to build next, wired in before day one.
Popular under this
- App Store and Play Store listings
- Crash reporting and analytics
- Review handling and release trains
- The first month after launch
How it runs
A demo every Friday, one fixed quote, and you own everything you pay for. The process is the same on every project — this is how it runs for consumer apps.
The problem on one page
A short call, then a one page brief we both sign: audience, the job the app does, what success measures.
A running skeleton in week one
Rough, real, on your phone. A prototype nobody can hold answers nothing.
Weekly demos to the store build
Every Friday you see working software. Scope changes are priced in writing before they are built.
Launch, then the first month
We stay through review, the first crash report and the first analytics read. Then you own everything.
FAQ
Asked before
most first calls
We price by phase with a fixed quote after the first call, not by the hour. A focused v1 typically lands in the range of a small team for two to twelve weeks; the quote tells you exactly.
Two to twelve weeks depending on scope. The first working build is on your phone inside week one either way.
We default to native for consumer apps because feel is the product. Where a shared codebase genuinely fits the brief we will say so and quote both.
Yes, about half our work starts that way. Week one is an audit of what is there, what is risky and what to keep.
Is this the work
you need done?
Tell us where you are, and we’ll tell you honestly if we’re the right team for it.