Unit suite
324 / 324
Passing in the latest reviewed snapshot.
PlanPilot - Review-first iOS Planning
PlanPilot turns a rough goal into a plan the user can inspect before anything is saved. The review step is the product: inferred tasks, timing, assumptions, and conflicts remain visible before optional calendar or reminder writes.
Public Beta Public TestFlight · still in development Source code private · public TestFlight beta
- SwiftUI
- SwiftData
- EventKit
- UserNotifications
- Local-first
- Provider seams
Planner matrix
53 cases
Kept green across the supported planning paths.
Evaluation corpus
9 / 9
Small, explicit behavioural checks rather than an adoption claim.
Localisation
459 keys · 10 languages
Complete in the verified localisation inventory.
Why review comes before automation
A planner can produce plausible output that still does not fit the user’s day. Automatically writing that output into a calendar turns a weak suggestion into cleanup work.
I built one reviewable plan contract for on-device, optional cloud, and offline heuristic planners. Every path returns information the interface can validate and show before the user confirms a write.
Product and engineering decisions
Nothing is saved before confirmation
Plan generation and calendar or reminder writes are separate steps, so the user remains in control of the final result.
Local-first remains useful offline
SwiftData holds the product state, and a deterministic heuristic path keeps basic planning available without a network call.
Cloud providers stay optional
Apple on-device models and optional BYOK cloud providers sit behind the same boundary instead of leaking provider-specific behaviour through the UI.
What the case study can show
The public beta demonstrates the product flow; a private walkthrough can go deeper into the implementation and tests.
- Review-before-save behaviour from goal entry through validation and confirmation
- Boundaries between on-device, optional cloud, and offline heuristic planners
- Calendar, notification, local-persistence, localisation, and planner-matrix test design
- Release gates and the distinction between simulator evidence and remaining physical-device acceptance
What the beta does and does not show
The public TestFlight link is live, but its presence does not erase the remaining work.
- PlanPilot is not released on the App Store, and no user-adoption or production-use claim is made.
- The public TestFlight page does not expose a build number, so it is not tied here to the repository’s current build.
- Physical-device verification for every calendar, notification, and on-device model path is not presented as complete.
- Cloud planning is optional and may use a user-supplied provider key; the app is not described as entirely offline in every mode.
Try the beta or request a walkthrough
The TestFlight beta is public. For recruitment review, I can also walk through the architecture and selected evidence while keeping the source repository private.