Build for the Bad Connection

Most technology is built in a room with perfect wifi, for a user imagined to have the same. That user is a fiction. The real one is on a patchy signal, on a shared phone, rationing a data pack by the day.

Build for the fast connection and you build for the few. The magic dies the moment it meets a real network — the video won't load, the form times out, the app assumes an "always-on" most of the country has never had.

So we build the other way round. Offline-first. Works on the old phone before the new one. Assumes the signal will drop, and holds the data until it returns. Less glamorous. Reaches far more people.

This isn't charity engineering. The bad connection isn't the edge case — it's the majority case wearing the disguise of an exception. Design for it and you don't just include more people; you build something sturdier for everyone.

Fast wifi flatters bad software. A weak signal tells the truth.

So before shipping, ask the question the demo never does:

Does this still work on the worst connection your user actually has?