Native phone applications

All project types · Shared launch

Build around life away from the desk. Android is the initial teaching target; the receiving agent establishes the route for the person's actual phone.

Projects to build

• Capture photographs for a report on site
• Workout companion
• Capture a spoken thought
• Home measurements and replacement parts
• Treasure hunt
• Practice notebook with recordings
• Field notebook for an interest
• Personal todo app
• Notes that reach the agent's workspace
• Chat with your coding agent from your phone

These are instructions for projects you can build with your coding agent.

Send your notes into your agent's workspace

Build a native Android notes application that synchronizes with the person's computer and saves ordinary, readable files where their coding agent works. Build it extremely well for collecting ideas away from the desk and returning to them with the agent. Follow the shared launch.

Start with the person's existing projects and notes. Find out where information should belong on their computer and how they usually return to an idea. Preserve the useful organization they already have.

Capture while away

Let the person type, dictate, or attach a photograph to a note. They can choose a project when the destination is clear and use an inbox when it is not. Make capture quick enough for a thought recorded between other activities.

Keep the note, its date, attachments, and useful context together. Let the person revise it, add another observation, and find it again on the phone. Save their work locally through interrupted or unavailable connections.

If they already have the voice-capture app, extend its collection into this experience. Keep recordings and transcripts with the same notes, so speaking becomes another way to contribute to the existing system.

Put the notes where the agent can read them

Synchronize notes into the person's chosen workspace as Markdown and ordinary attachment files. Use an arrangement that fits their projects and remains understandable in a normal editor. Preserve enough context for the agent to identify the note, its author, when it was made, and which project it concerns.

Use the existing coding agent's normal access to that workspace. Make the notes discoverable through appropriate project guidance while preserving the instructions and organization already there.

The person should be able to say, “Read the notes I made today. Let's work on the idea about the volunteer app,” and have the agent find the relevant text and photographs. Make that a real working experience delivered by this project.

Keep notes and requests distinct

Preserve the person's observations, quoted reference material, and explicit requests in their appropriate roles. A saved idea is available for discussion. Starting work follows the person's direction in the agent conversation or another work-request mechanism they deliberately add.

Keep the person's original note distinguishable from any later agent explanation or proposed plan. Let them organize or edit notes from their computer as well as their phone. Preserve changes from both places and make conflicting edits recoverable when they occur.

Make the connection dependable

Set up a private connection between the person's phone and computer. Tailscale is a natural option; reuse a suitable existing connection where appropriate. Explain what needs to be running for synchronization and what remains usable while a device is unavailable.

Show whether a note is saved on the phone, waiting to synchronize, or available on the computer. Reconnection should bring the current collection into agreement while preserving edits and attachments. Keep an export and recovery path under the shared launch's ownership guidance.

Use a note to begin real work

Handle the Android build, installation, and connection setup. Capture a note and photograph, leave the connection unavailable for a while, then let the material reach the computer. Open the resulting files and ask the existing agent to discuss them. Confirm that an edit made afterward remains available from both devices.

Explain how an agent's working context can include information gathered outside its chat window. The phone collects the person's experience; ordinary workspace files make it available for later collaboration.

A later extension can let the person explicitly mark a note as work for the agent to pick up while they remain away. The remote-agent chat app can also let them start that conversation immediately. Preserve the same notes and project context as those capabilities are added.

Capture a thought before you forget it

Build a native Android application for recording a spoken thought quickly and finding it later. Build it extremely well for moments when the person wants to capture something and return to what they were doing. Follow the shared launch.

Learn where those moments happen and what the person tends to record: an idea for writing, a question, something remembered after an appointment, or an observation while out. Make the first recording convenient on their actual phone.

Record first

Give the person a direct way to begin and end a recording, with clear feedback about whether the microphone is active and whether the audio has been saved. Let them name or organize the thought when they want to; capture should also work when they have no time for that.

Keep the original audio saved locally through unavailable connections. If recording is interrupted, retain what was captured and show where it stopped. The person should be able to return to the app and find the recording they just made.

Make listening back and adding a short note straightforward. Let them edit a title, associate the recording with a project, or leave it in an inbox for later attention. Keep the date and useful context with it.

Make the recording findable

Provide transcription through a suitable capability for the person's languages and device. Reuse available phone or computer capabilities where they fit, and explain any provider access or cost needed for the chosen route. Make the actual transcription connection part of the delivered project.

Keep recording usable while transcription is pending or unavailable. Show whether processing is waiting, underway, complete, or needs attention. The person can listen to the original throughout.

Let them find a recording through words in its transcript, its title, or an associated project. Bring the text and audio together so they can check a passage or correct a transcription mistake. Preserve the original recording alongside their edited text.

Give the collection a comfortable way to browse recent thoughts and find older ones. The person should be able to recognize a useful idea from its context before playing the whole recording again.

Organize when there is time

Let the person work through the inbox, add notes, assign projects, and keep the recordings they want. Give them an export that includes audio, text, and useful context in a form they can use elsewhere.

If they choose AI help with titles, summaries, or organization, keep those additions distinguishable from what they actually said. Let them change the organization and return to the original words whenever those matter.

Explain where recordings and transcripts are stored, what material reaches any external service, and how to recover the collection. Apply the shared launch's ownership guidance and provide understandable controls for storage and removal.

Use it through an interruption

Handle the Android build and installation, including the microphone access the app needs. Deliver a usable recording and transcription experience on the person's phone.

Capture a thought, leave the app, return, find it by a remembered word, and listen to the relevant recording. Try capture while the transcription connection is unavailable and let processing resume afterward. Judge the effort required to record and the ease of finding the thought again.

Explain why capture, transcription, and organization can happen at different times. The person learns that useful software can preserve an idea before they know where it belongs.

The synchronized agent-readable notes project can extend this collection later. If that workspace already exists, integrate these recordings with it. Preserve one coherent collection so voice capture becomes another way to contribute to the person's existing notes.

Talk to your coding agent from your phone

Build a native phone app through which the person can continue working with you on their computer while they are away. Build it extremely well, with a dependable conversation and useful control over real work happening in their projects.

Read this brief and follow the shared launch for setup, working skills, ownership, continuity, and learning guidance. Discover the build and installation route for their actual phone and carry it through to an installed application.

The experience

The person has a computer where their coding agent can work on applications. From their phone, they choose a project, open or start a conversation, and ask for something. The agent can inspect the project and carry out the work using its normal capabilities. They can read its response, discuss a decision, answer a question, and interrupt the work when their direction changes.

Imagine they notice an awkward screen in an app while out. They ask the agent to improve it, explain what bothered them, and then put the phone away. The computer continues working. When they return, they can see what happened and continue the same conversation.

Connect the phone app to the coding-agent environment the person already uses, with its existing account and model access. Carry the conversations, working context, and actions between the phone and that environment. The person should recognize the project and agent they work with at their desk.

Remote work should use the same project instructions, installed skills, and working knowledge. Use the installed agent's supported integration capabilities so the phone participates in real agent sessions and can accurately show what happened.

Stay oriented while away

Make it clear which project and conversation are open. Keep messages readable on the phone, with useful progress and results easy to follow. The person needs to understand whether the agent is working, waiting for an answer, finished, or currently unreachable.

Give their own actions equally clear outcomes: they can see whether a message has reached the computer and whether an interruption took effect. A lost phone connection and stopped agent work are different events; the experience should make that distinction understandable.

The conversation survives switching applications, locking the phone, and reconnecting later. When the person returns, show the current conversation and the work completed during their absence. Keep the underlying project and its work available from the computer as well.

Connect their own devices

Use a private connection suited to the person's devices. Tailscale is a natural fit for reaching their computer while away. Establish the connection as part of making the application useful, with access belonging to the person and the devices they choose.

Explain what needs to stay running on the computer for the agent to be available. Help the person understand any account, model-usage, or service costs involved in their chosen setup. Select the installation and connection approach from their actual environment; own those engineering decisions.

Build a foundation they can keep using

The complete experience here is remote conversation, real project work, direction, interruption, and returning to what happened. Give those capabilities sustained attention through focused steps, then put them together in an installed app the person can use from their phone.

Exercise the remote working experience, including leaving and returning to a conversation. Help the person try a useful change to one of their projects and understand where the result lives. Keep the interface centered on the work they are directing.

Include a connection from outside the computer's local network in that experience. Help the person understand the roles of their devices: the phone carries their conversation and control, while the computer runs the agent and does the project work. They should know how to restore the connection and continue when a device has been unavailable.

Later, they may want voice conversations, photographs, completion notifications, previews, or a convenient way to install something the agent built. Notes captured during the day can become material for a conversation. Choose a foundation that allows those additions while preserving the conversations and projects they already rely on.