Project BuiltDaily

Most fitness apps treat health data as a product to be aggregated, sold, or held hostage behind a subscription. BuiltDaily was scoped around the opposite premise: a focused, one-time-purchase companion that respects HealthKit as the source of truth and adds only the surfaces that Apple's own app leaves out — strength training, hydration, and a tab order you choose. The brief was to ship something an indie developer can stand behind for years without operating a backend.

BuiltDaily uses the native Apple type stack — SF Pro and SF Mono — so it inherits crisp rendering on every Apple device with zero font requests over the network. The marketing site mirrors the app: warm-white in light mode, deep neutral in dark, and a hero capsule that layers all five accent colors as a soft aurora wash. The palette is intentionally small but expressive, with each accent doubling as both a brand color and a user-selectable theme inside the app.

Type system

SF Pro Text · SF Pro Display · SF Mono (system stack, no web fonts)

Light surface

#FFFDF9 warm white · ink #14110D

Dark surface

#0E0D10 near-black · ink linen

Accent palette

Cobalt #3060F0 · Lavender #7C3AED · Electric #10B981 · Coral #FF8559 · Amber #E8A800

Default theme

Dark, with a persisted light toggle

The app is 100% SwiftUI on top of SwiftData, with HealthKit as its primary read/write surface and CloudKit private databases handling sync. There is no BuiltDaily backend — and there will not be one. App-specific records (workout templates, custom exercises, set logs, water history, goals, theme, tab order) sync between a user's own iPhone and iPad through their personal iCloud. Apple Health data syncs separately via iCloud Health, also fully managed by Apple.

Platform

iOS 18+, optimized for iOS 26

UI

SwiftUI · Swift Charts · UserNotifications

Persistence

SwiftData with CloudKit-backed ModelConfiguration

Health surface

HealthKit (two-way) — reads metrics, writes workouts and water entries

Sync

Private CloudKit database, scoped to the user's Apple ID

Servers

None. No accounts, no analytics, no third-party SDKs

Every screen is built to do one job well, and the user picks the order. The first tab is whatever opens when you launch the app — drag to rerank inside Settings, and the tab bar redraws to match.

• Today — a single live dashboard pulling from Apple Health: steps, active minutes, workouts, water, sleep, resting heart rate, flights, VO₂ Max, and weight
• Workout — templates, a curated exercise library by muscle group, live sessions with set/rep/weight/rest tracking, and a tap-to-review history
• Water — a customizable daily goal with three configurable quick-adds, custom amount entry, an undo-able timeline, and HealthKit sync
• Stats — Swift Charts visualizations across week, month, and year for every supported metric, including per-exercise volume and PR context
• Settings — appearance, accent color, units, tab order, visible cards, custom goals — every default is overridable, none are required

The privacy posture is structural, not a marketing line. Because there is no BuiltDaily server, there is no place where a breach could happen. HealthKit access is managed end-to-end by iOS — every permission is revocable inside Apple's Health app at any time, and BuiltDaily writes only the categories the user explicitly grants. The app ships with no analytics SDKs, no ad networks, no email collection, and no account system to compromise.