Shipping for Real Networks, Not Office Wi-Fi

A dispatcher console that works beautifully on a fibre connection in Lekki can be unusable to a driver in transit outside Kano. Most performance advice assumes a network that most of our users do not have. So we test against the network they do.

Assume the connection will vanish

Buffer locally, upload in batches, and design the server to accept late, duplicated, and out-of-order data as a normal condition rather than an error. A driver passing through a dead zone should backfill on reconnect - not disappear from the map and generate a support call.

• Client-side write buffer with a durable queue, flushed on reconnect.
• Idempotency keys on every upload so replays cost nothing.
• Deltas over snapshots - bandwidth is the scarce resource, not CPU.
• Offline-visible state: show the user what is pending, never a silent failure.

Budget the first paint in kilobytes

We set a hard byte budget for the first meaningful render and treat it like a test that can fail. It is a blunt constraint, and it works: it kills the fourth font, the analytics bundle nobody reads, and the animation library imported for one transition.

“Performance is not a polish phase. It is a constraint you either designed for or apologise for.”