Dispatch · 4 min read
The cold open.
How flexGrid's first 1.5 seconds got designed — and what we threw out to get there.
We spent a lot of v1 obsessing over what the first second and a half of flexGrid feels like. Not the install, not the first launch — the moment after you drop a folder onto the window. That window is the only one that matters; everything that happens after it is downstream of whether you believed the app worked.
02. What we threw out
Loading bars. Folder size warnings. Mascot prose. A blank grid waiting for the scanner to finish. The progressive scanner doesn't need a chaperone; it needs the first batch to be the right batch and to be drawn before anything else loads.
The first cell plays before the rest of the folder is finished counting.
cold-open-strategy-2026-05-20.md
05. What we kept
A cultivated first batch of around eight to twelve items, balanced for aspect ratio against the cells you're about to fill. AVPlayerLooper bound to a shared asset so the first loop seam is gone before you'd have noticed it. A breathing indicator in the status bar that says "working" without nagging.
On a folder of 25,000 files we'd been clocking the first batch at around 1.5 seconds. On a folder of fifty, it's faster than the eye can register. Either feels like the same gesture — open, drop, watch.
08. Why it matters more than it looks like it should
Apps that take a moment to load taught the audience to wait. flexGrid's whole pitch is the opposite — your media should be alive before you've finished asking. The cold open is the only place where we have to teach that, and the way we teach it is by not making you wait.
Sources cited
- — docs/cold-open-strategy-2026-05-20.md
- — docs/pre-release-findings-2026-05-16.md
Closing
Read the rest of the issue.
Same product, different angles. The feature catalog has the inventory; the dispatches have the why.