Engineering notes.
Written by the engineers who did the work.

New office, same core: our road from 2019 to 2026
In summer 2026 we moved into a quieter office. Our road from 2019 to now, in photos: people change, the core stays, and we keep improving.

Native, Flutter or React Native? Choosing a stack based on the application
Three recent apps, three different stacks. How we choose between native, Flutter and React Native by finding each app's main constraint first.

A 200× slowdown: how Core ML model encryption broke ANE acceleration
Turning on Core ML model encryption made our pose estimation 237× slower, with no error. How we traced it to the Neural Engine being skipped, and fixed it.

An AI-assisted delivery pipeline, from zero to hero
The AI-assisted pipeline behind a Flutter ordering app: a rulebook, five specialist agents, a clean-checkout CI gate, and the bug it still missed.

Taming runaway Combine publishers: killing redundant Core Data fetches
Every change re-read the whole recordings table, up to 10× a second. How Instruments found it, and how we now load once and update only what changed.

Showing real card data in a mobile wallet — without ever holding it
Showing a full card number and CVV in a mobile wallet without that data touching our servers: secure iframes, short-lived tokens and a strict CSP.

Resumable ML analysis of 4K/60 video
On-device ML analysis of 4K/60 video takes minutes. How it now pauses when the app leaves the screen or the phone gets hot, and resumes where it stopped.

When the OS revokes your GPU: background execution in a Core ML pipeline on iOS 26
iOS 26 lets apps keep using the GPU in the background, but not on the iPhone we needed. Why our Core ML pipeline now pauses cleanly and resumes instead.
Offline-First on Android · Part 1 of 4Offline-First on Android, Part 1 — Reads, Caching & Delta Sync
Part 1 of 4: how a smart-home Android app stopped waiting for the network, with one local source of truth in Room and a sync that pulls only what changed.
Offline-First on Android · Part 2 of 4Offline-First on Android, Part 2 — The Outbox Engine: Architecture & Draining
Part 2 of 4: an outbox that makes every offline edit survive the app being killed, and drains to the server in order.
Offline-First on Android · Part 3 of 4Offline-First on Android, Part 3 — Idempotency, Conflicts & Edge Cases
Part 3 of 4: expired tokens mid-drain, retries that must not duplicate, conflicts settled per field, and deletes you can take back.
Offline-First on Android · Part 4 of 4Offline-First on Android, Part 4 — Multi-Device, the Backend Contract & Operating at Scale
Part 4 of 4: syncing between devices, the contract the backend had to sign, when the app actually syncs, and what changes when one entity becomes ten.

