Independent product venture · Native iPhone + Apple Watch

DO Prepare on iPhone. Execute from your wrist.

Build and edit on iPhone, then run each step on Apple Watch. Timers, warnings and saved progress keep the workflow going through interruptions.

View live product

AudienceB2C

Independent ventureConcept → functioning native build

SurfacesiPhone + Apple Watch

Built withSwift · SwiftUI · iOS · watchOS · Claude Code

StatusSimulator tested · intentionally frozen before hardware validation

One product. Two surfaces.

Prepare on iPhone. Execute on Apple Watch.

The phone handles setup and editing. The Watch shows one step, its state and the next action.

iPhone · prepare

Make the workflow.

Create and edit workflows
Organize steps and metadata
Configure quantities, timers, and warnings
Manage what is ready on the Watch

sync →

Apple Watch · execute

Run the workflow.

Advance normal steps
Count quantity based work
Run timers and acknowledge warnings
Pause, resume, restore, and complete

Here is DO working

A full run stays on the wrist.

The run moves from the Watch library through each instruction to completion without returning to the iPhone.

The execution surface is deliberately narrow.

Each step gets the screen, the progress context stays visible, and the action that advances the task stays reachable. The goal is not to recreate the iPhone on a smaller display.

The idea

Stop treating the phone as the only place instructions can live.

The starting point was ordinary: follow a recipe, assemble something, set up a camera, service a machine. Your hands are busy, but the next instruction is on a phone you just put down.

DO explores a different split. Preparation stays on the larger surface where editing is comfortable. Execution moves to the wrist, where one glance and one deliberate action can keep the task moving.

I took DO from a product idea to functioning native software, designing the workflow across iPhone and Apple Watch and carrying it through native implementation and simulator stabilization.

Execution gets complicated

Not every step is simply “done.”

The working product had to preserve task state through interruptions, not only a sequence of static screens.

Quantity

Count progress from the wrist without leaving the instruction.

Timer

Track against an absolute end time so reopening does not restart the wait.

Warning

Require a deliberate acknowledgement before the related instruction continues.

Pause and restore

Persist the active session so an interruption does not reset the workflow.

I built it native

The design decisions had to survive implementation.

SwiftSwiftUIiOSwatchOSClaude Code

I conceived and designed DO, then used Claude Code as part of an AI assisted development workflow to implement and iterate on the native iPhone and Watch apps.

The build includes workflow creation and editing, Watch synchronization, execution state, quantities, timers, warnings, pause and resume, persistence, session restoration, completion, and synchronization of completed sessions back to iPhone.

Taking it beyond a prototype

Simulator QA exposed product problems static screens could not.

The useful part of stabilization was seeing where state, persistence, and system behavior could contradict what the interface promised.

What broke

A completion haptic could fire at the wrong moment.

Why it mattered

On the Watch, the haptic is part of the interaction feedback. A false completion signal makes the product state feel untrustworthy.

What changed

The completion signal was tied back to the actual timer completion condition.

What broke

Independent persistence writes could land out of order.

Why it mattered

A restored session could show an older step even after newer progress had already been made.

What changed

Persistence was changed so the latest execution state remains authoritative.

What broke

A stored model change could make older data unreadable.

Why it mattered

Evolving the product could otherwise turn existing saved workflows into invalid state.

What changed

The storage path was hardened so saved workflow data can survive model evolution.

Where I stopped

Functioning venture concept, intentionally frozen before distribution.

I stopped after native implementation and a substantial simulator stabilization pass. The next meaningful milestone would have required physical Apple Watch validation and distribution.

View live product

Built

Native iPhone and watchOS apps plus the workflow and session loop between them.

Tested

Simulator based QA, build stabilization, state restoration, and interaction review.

Not pursued

Physical Apple Watch validation, TestFlight distribution, and App Store release.

Not claimed

No public users, traction, revenue, adoption, or business impact.

Next venture