design + mobile
When the app does not exist yet, designing flows first saves rework in build.
~/Overview of the studio and its lifecycle view~/companyWho we are and what we will not claim~/servicesMobile, design, websites, release help~/planLocal checklist tool for subscription products~/methodHow work moves and how we judge it~/notesSearchable notes and checklists~/supportRaise a support request~/contactProject enquiry or phone callback~/privacyForms, hosting, local storageArrow keys move · Enter opens · Esc returns you where you were
~/services
Each one can stand alone or join up with the others. IT support sits alongside on its own page.
mobile
Native-feeling apps for iOS and Android, built so that sign-in, plan status and payments behave predictably.
design
Flows and interfaces that make it obvious what someone gets, what it costs and how to change their mind.
web
Fast, readable websites: product pages, pricing, help centres and the legal pages that sit beside them.
publishing
Help getting a build from finished to published, and keeping later updates calm.
When the app does not exist yet, designing flows first saves rework in build.
Store listings link to a website; writing both together keeps the promises consistent.
After launch, IT support covers the devices and tools your team uses to run it.
We build the app and web side and connect to the services you choose. We do not present ourselves as a payments or infrastructure provider.
Often, yes. We would start by reading the code and release history before agreeing anything.
No. Scope varies too much. A conversation comes first, then a written estimate.