Independent products
HomePilot: Home & Auto
A native iPhone application bringing recurring home maintenance, vehicle care, and household subscriptions into one place.
- My role
- Creator & iOS Developer
- Context
- Independent iOS product · HomePilot: Home & Auto
- Toolkit
- Swift · SwiftUI · SwiftData · Supabase · StoreKit
- My contribution
- Product design, SwiftUI development, local data handling, and optional Family Sync.
- Evidence shown
- Screenshots and architecture from the August 2026 product archive. They may differ from the current App Store build.
Home and vehicle maintenance
A filter change, a vehicle service, an insurance renewal, and a household subscription are different kinds of obligations. HomePilot brings them into a single native iPhone experience instead of leaving them scattered across notes, calendars, and memory.
My work spans the product’s interface, application architecture, data handling, and release iteration. Home, Vehicles, Calendar, Subscriptions, and Settings give each task a clear place while sharing the same underlying maintenance history.
Recording maintenance and reviewing history
The completion flow is designed around one contextual action followed by a guided form. A completion date and any required vehicle mileage come first; notes, costs, service details, and photos remain optional.
Saved completions open as readable records, with editing behind an explicit action. This separates inspecting history from changing it. Shared visual components, semantic feedback, and reduced-motion support carry the same interaction language between screens.
Subscription tracking adds recurrence, renewal reminders, and spending views without implying that HomePilot cancels a provider’s subscription or automatically converts currencies.
Inside the maintenance data rules
SwiftUI presents the interface and SwiftData persists the local graph. Completion records retain their own mileage: an older, lower reading can belong in history without reducing the vehicle’s current odometer.
Browse and detail views use native push navigation. Save/Cancel editors use modal flows, preserve input on errors, and keep optional details out of the primary path.
Keep local use independent. Make sharing deliberate
The documented Family Sync implementation combines an on-device cache with Supabase-backed shared records, Apple sign-in, and StoreKit entitlement handling. The owner activates a Family, while invited members join the shared space.
Disconnecting a device preserves an independent local snapshot. Recovery, membership permissions, attachment storage, and offline changes each need explicit behavior; they are not just a sign-in screen added to a local app.
- SwiftUI actions
- SwiftData + pending changes
- Family Sync engine
- Supabase records + private attachments
Sync, reminders, and portability
The source describes last-write-wins record convergence, reset epochs to stop stale devices resurrecting deleted data, and attachment quota reservations. These contracts are distinct from proof of current backend activation.
Reminders are delivered through device-local UserNotifications; remote APNs delivery is not connected in the documented snapshot. Private reminder choices and device notification permission have different scopes.
Versioned .homepilot exports and owner-only cloud export jobs provide a portability path. Support intake and export services are documented implementation work, with end-to-end operating checks remaining version-specific.
The product lives in the details
The difficult work is often the behavior between screens: what survives a failed save, what a disconnected device retains, and what happens when an old record is edited. HomePilot made those contracts as important as the visual interface.
The release ledger records version 1.0.1 as live in August 2026, while later 1.1.x entries are submission candidates. The screenshots shown here are historical product evidence, not a claim that every pictured flow matches the latest build.