Apps

The apps I build, with the same method I sell.

Every one of these went through the strategy work on the services page first: who it's for, what they actually struggle with, what goes in version one. If I'm going to tell founders to do it, I have to do it too.

iOSComing soon
Expected in November

Dayletter

A symptom diary you talk to. Say how the day went, and the app writes it up and turns it into a report you can hand to your doctor.

For people with a chronic illness who are too tired to fill in a form. Nothing leaves the phone: no server, no account.

iOSComing soon
Looking for beta testers now

Neori

Type what you need. Neori writes a meditation for exactly that and reads it to you.

Instead of searching a library for something close enough, you get one written for the sentence you typed. Saved to your library, shareable by link.

iOSComing soon
Expected in December

Actually Keto

A keto tracker that puts your fat, protein and carb ratio first.

Food search, a planner, recipes, stats, and your workouts from Apple Health. Built for people who already know what keto is.

macOSComing soon
Looking for beta testers now

Coast

Your app strategy, worked out on your Mac. Coast walks you along a strategy map, milestone by milestone, and writes up the documents as you go.

The same framework as the free course and the workbook: ten milestones, from grounding the idea to getting it out the door. You answer the questions and make the calls; Coast keeps the record.

Tools

Things I built for building the apps

Editdesk

Open any page, click the text, retype it in the page's own font, press Enter, and it's saved to the source file. For people who build pages with AI and don't want to spend credits changing one word. Open source, MIT.

Download ↗

Beacon

A report button for your Mac or iPhone app. Your testers press it, and you get a GitHub issue that already says what they expected, what happened, how they got there and which build they were on.

Download ↗

Coast Standards

Every piece of software Up Coast builds follows one written set of engineering rules: what comes first, how code is structured, what a test has to prove, how a change is reviewed. They are source-available under their own licence, so you can read them and use them unchanged.

Download ↗