Maintain iOS
Maintain is a native iPhone app and backend scaffold for weight maintenance after loss or major body transition. The product is intentionally framed around staying inside a user-defined maintenance range, understanding short- and long-term fluctuation, and keeping GLP-1 medication context descriptive rather than prescriptive.
Narrative
Maintenance instead of loss
Maintain is a native iPhone app for people who are trying to stay steady after weight loss or another major body transition. The project is built around a user-defined maintenance range, short- and long-term fluctuation awareness, and GLP-1 context that stays descriptive rather than prescriptive. Its core product choice is to make the question "am I still inside my range?" easier to answer without turning normal day-to-day movement into failure.
Current app surface
The observed iOS experience has three main entry states: a sign-in gate for configured builds without a session, onboarding for profile and range setup, and a five-tab returning-user shell. Home carries range status, daily logging state, maintenance context, 30-day fluctuation, HealthKit pulse, recommendations, and quick actions. Log captures weigh-ins, medication check-ins, workouts, and medication plans. Trends makes the maintenance band and fluctuation pattern visible. Activity separates imported movement from manual routine context. Profile concentrates setup editing, HealthKit state, export/share actions, and sign-out.
System shape
The app is local-first, with SwiftUI screens reading through a central AppModel that coordinates SwiftData persistence, auth state, HealthKit import, export manifests, and remote sync. The backend is a Cloudflare Worker using Hono and Zod over a Neon repository, with authenticated routes for profile, maintenance range, weights, dose events, workouts, schedules, trends, sync cursor, and exports. The architecture keeps sample-rich states in test and visual-checkpoint fixtures so real profile creation does not quietly seed fake support data.
Release boundary
The strongest evidence is the local iOS route graph and staged backend contract, not a fully verified public production launch. Source docs mark the intended production API hostname and production Worker reachability as blocked in the recorded account context, and App Store/TestFlight progress depends on App Store Connect access. Human review remains important because the product is health-adjacent: wording should preserve privacy, user control, and descriptive medication context without drifting into unsupported clinical guidance.
System design
System surfaces
Native iOS app
SwiftUI iPhone app with sign-in, onboarding, Home, Log, Trends, Activity, and Profile surfaces.
Staging API
Cloudflare Worker staging endpoint for authenticated profile, sync, export, and route smoke verification.
Visual checkpoint packet
Repo-owned simulator screenshot harness covering the core native app surfaces.
Implementation stack
iOS
- • SwiftUI
- • SwiftData
- • Swift Charts
- • HealthKit
- • TipKit
- • XcodeGen
Backend
- • Cloudflare Workers
- • Hono
- • Zod
- • Neon Postgres
- • Neon Auth-compatible JWKS
- • R2
- • Queues
Verification
- • Makefile gates
- • XCTest UI capture
- • SnapshotTesting
- • Vitest
- • backend staging smoke
- • docs manifest/link checks
Artifacts
Maintain app and backend loop
The native app captures maintenance context locally, syncs authenticated changes through Worker routes, and uses staging/TestFlight gates before broader release decisions.
Maintain validation and surface-capture loop
How Maintain turns native iOS and backend work into reviewable evidence: regenerate the Xcode project, run simulator surface capture, verify docs/backend/iOS gates, check staging when credentials are available, and keep TestFlight/App Store blockers explicit before release decisions.
Maintain product brief
Product framing for a private iPhone app centered on maintenance range confidence, fluctuation awareness, GLP-1 context, and personal maintenance history.
Maintain MVP requirements
MVP requirements for onboarding, customizable maintenance range setup, local persistence, dashboard interpretation, logging, trends, activity, profile, and backend scaffold scope.
Maintain iOS architecture
Client architecture showing the SwiftUI app shell, SwiftData container, AppRootView states, AppModel coordination, HealthKit import, export manifests, and local-first sync seams.
Maintain backend architecture
Worker and Neon backend architecture for authenticated profile, range, weights, dose events, workouts, schedules, sync cursor, trends, and export flows.
Maintain environments and deployment state
Environment evidence for local, preview/staging, and intended production API/auth targets, including the recorded production reachability and Worker-account blockers.
Maintain Home surface evidence
Screenshot evidence of the returning-user Home surface with maintenance status, target/drift/recent values, trend chart, HealthKit pulse, and tab navigation.
Maintain current-state journey audit
Journey audit evidence covering the sign-in gate, onboarding, returning-user tab shell, HealthKit states, export states, and unverified hosted/live-route boundaries.
Visual evidence
Key dates
Product brief and PRD describe the maintenance-specific user, range confidence, fluctuation awareness, medication context, and private-by-default posture.
Maintain source docs record merged Logbook, branch recenter, sync, and clean-main validation repair streams.
Maintain is reviewed from current source evidence as a first-class project candidate with the public record focused on product, app surface, architecture, and release boundaries.