Independent Engineering
Designing, engineering, and shipping my own products, from iOS apps to the infrastructure they run on.
- Where
- Self-directed
- When
- Ongoing
- Scope
- Product Engineering · iOS · Infrastructure
- Written
- 8 of 8 sections
Context
Products built outside the day job, end to end: design, code, infrastructure, distribution, and support. Nobody to escalate to and no one else to blame.
This page is the why. The evidence, every build log and postmortem, lives in the lab on zckr.dev.
Problem
Leading engineers is easier when you still know what the work costs. Independent products are where that knowledge stays current, and where ideas get tested before they are recommended to anyone else.
Constraints
Evenings and weekends. One engineer. Real users who notice when something breaks, and in Stagger's case a tournament date that does not move.
Role and responsibilities
Everything: product, design, engineering, operations.
Technical approach
- collect.ShippedA personal cataloging app for iPhone and iPad. No accounts, no servers, private by design. Build log
- StaggerShippedA private, invitation-only golf tournament PWA: live scoring, an audited drinks economy, and offline tolerance built for a weekend with no signal. Build log
- PictrShippedA free, open-source iPhone app for reviewing and cleaning up your photo library. On This Day, a swipe deck, and cleanup that learns what you keep. Build log
- felt.BuildingEight cue games in one offline HTML file, 8-ball to snooker and three-cushion, with a CPU that has personalities and a multi-season career. Build log
- zckr.devThe lab: what is being built, what shipped, and what broke. The canonical record for every product above.
- acker.cloudThis site. Static Next.js, a validated content snapshot, and a contrast gate that blocks the build.
Key decisions and tradeoffs
- Numbers are derived, never typedacker.cloud
- Every count this site prints is computed from the published snapshot, so a figure cannot outlive the content that justified it.
- Accessibility blocks the buildacker.cloud
- Every colour pair is measured against WCAG thresholds before the build runs. A failing ramp does not ship.
Outcomes
Each product's status is in the registry above, read from zckr.dev. acker.cloud ships as fully static HTML with every route prerendered.
Lessons learned
A real deadline is the best architecture review there is. The weekend happens on its date whether or not the sync works, and there is no rolling back a tournament.
Stack
- Swift
- Next.js
- TypeScript
- Supabase
- Postgres
- Proxmox