What I build with

Swift and SwiftUI for everything native. SwiftUI moves fast enough to justify itself once a layout stops fighting it, and dropping to AppKit or UIKit for the parts it handles badly is cheaper than adopting a cross-platform framework and losing the platform's own behaviour.

• Swift 6
• SwiftUI
• AppKit
• Vision
• PDFKit
• Core Location
• Foundation Models

Next.js on the App Router with TypeScript in strict mode. Most of these sites are static exports or mostly-static pages, because a personal-scale product should not need a server running to show someone a page. Tailwind handles styling; a small token layer in CSS custom properties handles theming, so light and dark are one system rather than two stylesheets.

• TypeScript
• Next.js
• React
• Tailwind CSS
• Zustand
• Vite

Postgres when relations matter, SQLite at the edge when they do not. Prisma where the schema is the source of truth. FastAPI when the work is genuinely Python-shaped — numerical models and hazard engines — rather than reaching for one language everywhere.

• Postgres
• Supabase
• Prisma
• Turso
• SQLite
• FastAPI
• Python

Model access sits behind a provider abstraction in every project that uses it, so a model can be swapped without touching feature code. On Apple platforms the preference is on-device inference through Apple's own frameworks: no key to manage, no network round trip, and nothing to explain in a privacy policy.

• Anthropic Claude
• Groq
• Apple Foundation Models

Vercel for the web, App Store Connect for native, GitHub for everything. Deployment is boring on purpose — the interesting problems should be in the product, not in getting it in front of people.

• Vercel
• App Store Connect
• GitHub
• Xcode