Apple Photos & external drive images indexed and bridged via immutable UUIDs.
Family Captions
A mobile-first collaborative web platform built ahead of a family reunion to preserve perishable oral history across 20,000+ photographs—elevating an early prototype kicked off by my father-in-law Chris into a hardened, zero-lock-in multi-user archive that also sparked my lasting love for Neo-Brutalist web design.
Concurrent SQLite WAL schema with transactional edit audit history and skips.
Only 4 production npm packages—zero ORMs and zero runtime bloat to maintain.
Streaming selective ZIP archives pairing photos with human-readable story files & JSON.
Mini-App: Light-Table Captioning & Audit History
caption_history Audit Drawer
.txt ZIP Sidecar Preview
Turning a Stakeholder Sketch Into a Multi-Generational Tool
Elevating Chris's Foundation
Chris initiated the vision, wrote the reunion brief, and spun up an initial prototype on his Mac to rescue fading family memories. Rather than starting over, I treated his brief and instincts as the spec—hardening concurrency, ingesting cross-platform uploads, adding audit trails, and making it rock-solid for every relative's phone.
Simple Name Entry Meets Protected Uploads
Requiring passwords or app store installs stops older aunts, uncles, and grandparents cold in a living room. Contributors simply enter their first name to browse, verify, and add memories—while batch media uploads sit cleanly behind a separate passphrase gate.
Preserving Disagreement Rather Than Overwriting
When two siblings remember different years or faces in a photo, both guesses are vital historical clues. Omitting unique constraints per contributor lets multiple relatives save memories side-by-side tagged as "pretty sure" or "just guessing", with existing notes displayed above the form for corroboration.
How Reunion Readability Sparked Neo-Brutalism
Polishing this utility-first interface around IBM Plex Mono, a strict
16px minimum font floor, sharp 0px radii, high-contrast monochrome
surfaces, and oversized 52px buttons let historical photos stand as the sole
source of color—and sparked my love for Neo-Brutalism.
Temporary Work Surface & Concurrent Data Layer
Apple Photos + Browser
Python (osxphotos + sips) bridges Chris's Mac library while phones/PCs upload through Sharp + Multer.
node:sqlite (WAL)
Built-in synchronous SQLite in Write-Ahead Logging mode with 4 UUID-anchored tables & edit history.
5 Focused Screens
Sequential queue with history back-stack, 60-item paginated light-table grid, peer notes, and batch upload.
Streaming ZIP + Sidecars
archiver streams collision-safe {stem}_{uuid8}.jpg photos alongside readable .txt stories & JSON.
UUID-Anchored Archive Safety
Photos never touch private iCloud credentials online. Records key on immutable Apple
Photos UUIDs (or randomUUID() on browser uploads), preventing classic
IMG_0001.JPG collisions and enabling future round-trip metadata write-back.
Four-Table Relational Core
Models photos, multi-author captions (with SQL-checked
confidence labels), composite-key skips via INSERT OR IGNORE so
skipping unfamiliar faces never blocks anyone else, and append-only caption_history.
Zero Router Bloat on Frontend
Instead of dragging in heavy state managers or routing dependencies, the React SPA coordinates sequential captioning, "My Notes", 60-thumb pagination, and batch downloads cleanly with return-position tracking so light-table browsing never loses your place.
Built for Reunion Wi-Fi, Safety & Longevity
Non-Destructive Edit Auditing via Atomic SQL Transactions
Allowing inline edits on "My Notes" creates risk if a relative accidentally erases an
earlier story. Refactoring caption updates to copy the existing row into
caption_history inside an explicit BEGIN / COMMIT / ROLLBACK
SQLite transaction ensures past memories are always recoverable from a clean
on-demand drawer.
Zero-Compile Portability Using Native node:sqlite
Because native C++ bindings (better-sqlite3) failed V8 compilation on
Chris's Node v26 runtime, migrating to Node's built-in node:sqlite
(DatabaseSync) paired with WAL concurrency eliminated native
build chains completely across macOS development and Linux hosting.
Hybrid Media Pipeline: iCloud Fallback + EXIF Auto-Rotation
Because iCloud-optimized Macs frequently mark non-destructive edits without caching
rendered files locally, the Python osxphotos extractor gracefully falls
back to unedited originals instead of skipping precious photos. Meanwhile, browser
uploads on Windows, Android, or iOS pass through sharp().rotate() to bake
smartphone EXIF orientation directly into standardized 1920px views and
400px grid thumbnails.
Streaming Portable Exports & WCAG Contrast Hardening
Selectively exporting albums pipes directly into HTTP responses via streaming
archiver ZIP generation without buffering large photo sets in memory.
During UI hardening, replacing faded opacity: 0.35 disabled styling with
opaque neutral grey (opacity: 1) preserved strict WCAG legibility for every
family member.
Constraints & Architectural Solutions
| Challenge | Context & Constraint | Engineering Decision |
|---|---|---|
| Node v26 SQLite Builds | Native C++ addons failed against modern Node v26 headers across dev environments. | Adopted built-in node:sqlite (DatabaseSync) with WAL concurrency—zero native compile steps. |
| Uncached iCloud Edits | iCloud Macs flag edited images whose rendered outputs may not exist locally. | Built a fallback path in Python osxphotos exporting unedited originals rather than dropping photos. |
| Non-Mac Relatives | Family members on Android, Windows, or phones couldn't use local macOS export scripts. | Engineered cross-platform browser upload ingestion using multer + sharp with instant SQLite registration. |
| Multi-Author Memory Edits | Inline edits risked losing earlier nuances; conflicting stories needed equal visibility. | Logged immutable snapshots into caption_history inside transactions and displayed peer notes above forms. |
| Long-Term Family Custody | Oral history must outlive any single web server or framework. | Built streaming collision-safe ZIP archives bundling JPEGs, human-readable .txt sidecars, and JSON manifests. |
Falling in Love with Neo-Brutalism
More than any database trick, hardening Family Captions permanently shaped my design compass. Stripping decorative fluff down to honest monochrome typography, crisp rules, WCAG contrast even on disabled states, and giant clickable targets directly helped my family interact naturally—and inspired the Neo-Brutalist portfolio you are exploring right now.
"Bridging 'it works on a laptop' to 'my whole family can preserve 20,000 memories together' is why building software from scratch feels like magic."
Built for Every Generation & Screen
Running on four core dependencies preserves clarity alongside strict interface
guardrails: a 16px text floor, 52px hit targets, zero
faded opacity on disabled states, full keyboard navigation across queues, and clean
UUID round-trips ready for offline reunion hosting or Apple Photos write-backs.