Tools I build with

I drive Xcode mostly through xcodebuild on the CLI for archives + uploads, but the IDE is where the actual writing happens. Live previews on for SwiftUI work. Instruments for performance dives.

~380K lines of Swift across the portfolio. SwiftUI is the default; UIKit only when SwiftUI hits a wall (custom collection-view diffing, complex gesture interactions). Swift Concurrency for everything async — async/await, actors, AsyncStream.

SwiftData for the local store — DupeOut's cluster cache, Closet's wardrobe, EatWisely's meal log. CloudKit private database for cross-device sync. The "no backend" architecture means I never run a server, never pay for hosting, and Apple controls the data plane.

CHSharedKit 2.5 swapped MLX in as the on-device LLM backend after eastriverlee/LLM.swift went 404. Qwen 2.5, Phi-3.5, and Llama 3.2 all run cleanly on Apple Silicon. The unified backend powers AI features in LiftCoach, EatWisely, Closet, and TrainInsight without any of them touching the network.

DupeOut's whole engine is built on Vision: VNFeaturePrintObservation for similarity, Laplacian variance for sharpness, luminance histograms for the Bad Photos detector. PhotoKit handles the actual library access + iCloud Photos download orchestration. None of it touches the network.

DupeOut Build 62 added 4 intents: Scan, Show Duplicate Count, Open Trash, Scan With Preset. The "Show Count" intent answers Siri without launching the app — it just reads from UserDefaults (the foreground app writes after every successful scan). Tiny code surface, real value.

I drive the architecture, the design decisions, the cadence. Claude Code executes the boring keystrokes — implement-this-helper, refactor-this-API, write-the-docstring, run-the-tests, archive-and-upload. Iteration cycle dropped from days to minutes for routine work. The savings get redirected into more careful design + more thorough testing.

For visual work where I need to see + manipulate the file directly. Tab-complete is excellent for SwiftUI view scaffolding. Pairs with Claude Code for the larger refactors — Cursor for inline iteration, Claude Code for orchestration.

Today / Upcoming / Areas. The thing I love is that it stays out of my way — no notifications, no streak counters, no AI suggestions. Just a place where I can drop something and trust it'll resurface when I asked it to.

Light usage — most UI design happens in SwiftUI directly because the iteration loop is faster (Xcode preview is instant, Figma → Xcode is a translation step). Figma earns its keep for: marketing visuals, app icons, App Store screenshots, anything that needs to live outside the running app.

Each app has a scripts/build-and-upload.sh that runs xcodebuild archive, exportArchive, altool upload, then PATCHes TestFlight What-to-Test notes via the JSON API. End-to-end ship is one command. ASC API key + issuer ID live in a gitignored .env per app.

Plain HTML + Tailwind CDN + Inter font. No Hugo build step on the recent pages. Each per-app site lives at /apps/<name>/ with its own index.html, privacy.html, support.html, style.css. Push to master, Pages deploys in 30 seconds.