upKeep
upKeep
Case study

A working product · In pre launch testing

A home never runs out of things that need doing.

upKeep makes that manageable. It’s a real app, designed and built end to end. These screens are from my phone.

  • Idea to working app
  • Designed and built by me
  • Running on a real phone

The problem

The hard part isn’t remembering. It’s knowing what deserves attention today.

A home has hundreds of small jobs. Some repeat, some come round once a year, some are overdue, and some nobody has thought of yet. Drop all of that into an ordinary task app and you get one long list that’s easy to ignore.

upKeep starts from a different question: what actually needs attention? The answer has to arrive without becoming another source of stress.

How the product works

One loop, four kinds of work.

  1. Discover

    Find jobs you hadn’t thought of.

  2. Plan

    Choose what gets scheduled, and what doesn’t.

  3. Do

    Pick up what fits the time you have.

  4. Record

    Log what was done, when, and by whom.

  5. Repeat

    Recurring jobs come back when they’re due.

The system handles recurring jobs, overdue jobs, jobs nobody has scheduled yet and jobs you’ve only just discovered. Each is treated differently, which is what stops it turning into one giant list.

The product

What it does, and the problem behind each part.

Home

What needs attention now?

Home shows today’s jobs, how long they’ll take and how many are done. Not the whole backlog. Overdue work gets a plain label, not an alarm.

Below it: the week ahead, what’s coming up, and the state of the house. The greeting even gets a fresh saying every day, as a small touch.

  • I have time

    When you’ve only got 20 minutes.

    People rarely have a free hour. This finds the jobs that fit the time you actually have, so a spare ten minutes still gets used.

  • Walk around

    Find the jobs you didn’t know you needed.

    Move through the house room by room and add jobs as you notice them. It solves a different problem to scheduling: you don’t know what you don’t know.

  • Catch up

    Catch up without creating another obligation.

    Some work has never been scheduled. Catch up suggests it without committing you. A suggestion isn’t a schedule, and you decide what enters your system.

Places and calendar

One system across every place.

A home, a weekender, a workshop: each place keeps its own workload and history, and the calendar pulls them into one chronological view.

It’s a list of what’s coming, not a grid to squint at. Overdue work sits at the top.

Built, not just designed

None of this is a prototype.

These are screens from the running app, not concepts. Behind them is working software with its own logic and data.

  • Working data, not placeholder content
  • Scheduling that knows what’s due, and when a job turns urgent
  • A library of jobs to bring into your own system
  • A household model with multiple places
  • History of what was done, when and by whom
  • A real mobile experience, on a real phone

Your idea

upKeep is one example. Yours will have a different problem to solve.

Most ideas start as a sense that something should exist. I work through it with you until it’s clear what the product needs to do, then design it, build it, and test it on a real device until it holds up.

  1. Define

    Work out the product

    What it does, who it’s for, and what it shouldn’t try to do.

  2. Design

    Shape the experience

    How it looks, how it moves, and how it behaves in real use.

  3. Build

    Make it work

    Real logic and real data, not a clickable mock-up.

  4. Refine

    Test it on a phone

    Use it, find what’s wrong, and fix it.

Have an app idea?

Bring me the idea. We’ll work out what it needs to become.

← Studio104