# Build a todo app around how you get things done

Build a native Android application for remembering, organizing, and completing the person's tasks. Build it extremely well for their actual habits and responsibilities. Follow the [shared launch](../shared/launch.md).

Learn what they currently forget, where they keep lists, and when a reminder is useful. Start with real examples: a project, the next hardware-store visit, preparations for camping, or a recurring household routine. Let those examples shape the app.

## Capture a task while it is in mind

Give the person a quick way to record a task with useful notes or a photograph. They can assign a project or situation immediately, or leave it in an inbox to organize later. Make finding and changing a recently added task easy.

Keep enough detail with the task to do it later. “Buy batteries” can carry a photograph of the label and the quantity needed. A task about contacting someone can retain the relevant information and the reason for the call.

Let the person decide what is a task, what belongs as supporting material, and what can be discarded. Preserve their notes as tasks move through the app.

## Bring up the right work

Support the ways the person recognizes an opportunity to act. A list for a particular shop, a project view, and work due before an event can each be useful. Dates and reminders should serve the task's real timing.

Make it easy to see what they can do now, what they intend to do later, and what is waiting on something else. Give them a practical way to reorder work or change their mind while retaining the details they need.

Use notifications where the person wants them, with clear control of timing and repetition. A dismissed reminder and a completed task should have different meanings. Keep the task available when a reminder has passed.

## Make recurring routines useful

Let the person reuse a routine while starting a fresh instance of its work. Camping preparation may include charging equipment the night before, packing it in the morning, and buying supplies during an earlier errand. Preserve those relationships in a form that makes sense to them.

Keep completed instances available when they help the person remember what happened. Changing the routine for next time should preserve the history of a previous occasion. Let them decide which details carry forward and which belong only to this instance.

Make completion easy to record and mistakes easy to undo. Give the person a clear way to postpone, cancel, or resume work according to their own habits.

## Keep the app ready when needed

Save tasks and supporting material locally so the app remains useful through unavailable connections and ordinary interruptions. Make the important information readable and convenient to reach on the person's phone.

Handle the Android build and installation, including any notification setup the chosen experience requires. Provide an export and recovery path under the shared launch's ownership guidance.

Use a real errand or routine to judge the result: capture tasks, find the relevant list, complete part of it, change a plan, and return later. Improve how the app brings the relevant work back to their attention.

Explain how the same task can have a purpose, a situation, and a useful time to act. The person learns to describe the circumstances under which software should bring information back to them.

A later agent connection can help organize tasks or take on explicitly delegated work. Keep the actor clear: the person buys the batteries; the agent can research which replacement is needed. Preserve the tasks and their history as those capabilities are added.