Ready
Start a focus interval or take a reset immediately.
Flagship native product case study
A local-first macOS utility that turns the moment a focus interval ends into one practical reset—without opening a dashboard or asking the user to invent the next step.
Implementation
Locally verified
Role
Product, UX, SwiftUI, release
Runtime
Native macOS 14+
Year
2026
Product premise
State and available time narrow a reviewed local catalog to one optional action. Completing or skipping it closes the loop and starts focus again.
reviewed activities
accounts or network calls

The interface stays compact because the lifecycle is explicit. One store owns the graph on MainActor; dates remain the source of truth when the app wakes, relaunches, or observes time changes.
Start a focus interval or take a reset immediately.
A wall-clock deadline remains authoritative through sleep and relaunch.
The app recommends one safe activity; a notification is optional.
Done, Skip, or natural expiry records variety and begins focus again.
Breaking returns to Focusing, so the fourth state closes the loop back to the second.

Notifications and launch-at-login improve reach, but neither controls the product state. Their adapters report real macOS status while the focus and break lifecycle continues locally.
Denied notifications never stop a deadline from becoming break due.
Quiet hours suppress reminders, not local timer progression.
Activation, wake, clock, timezone, and day changes share one reconciliation path.
Legacy preference payloads remain backward-compatible and fixture-tested.
Started-at and ends-at dates make the interface a projection of elapsed wall time, not a fragile chain of timer callbacks.
Office-safe and mindfulness preferences are never relaxed. State, duration, and novelty soften only through an explicit fallback order.
A versioned JSON catalog keeps wellness copy inspectable, activity identities stable, and the complete version-one loop offline.
Keyboard defaults, stable progress semantics, adaptive native layouts, and named accessibility actions are part of the workflow contract.
54
The suite covers the state graph, persistence, catalog policy, quiet hours, permission reconciliation, and the release packet. It does not substitute for a signed-build lifecycle matrix or beta.
validated local activities
Every default-filter state and duration intersection is covered, with named human review for version 0.1.0 (1).
appearance and accessibility captures
Light, dark, large text, contrast, transparency, recovery, and Settings presentations are recorded as engineering evidence.
runtime network dependencies
No account, backend, analytics, advertising, remote content, or network entitlement is part of version one.
Notification denial is shown as a state, not an error trap. Quiet hours, interval controls, activity preferences, and system integration stay native, inspectable, and reversible.
These are current deterministic fixture captures. Final public media must still come from the exact signed candidate.

Locally verified
Help desk workers move from a focus interval into a useful micro-break without adding a dashboard, an account, or another decision at the moment their attention is already depleted.
Earlier work remains available for context and does not represent my current technical scope.