Building for Weak WiFi and Slow Devices

Developer laptops are fast. Developer internet is fast. Developer testing environments are fast. Real users are not always on developer setups.

We test on old hardware. We throttle the connection. We turn off wifi entirely and check what still works. Most of our tools pass that test. The ones that do not get fixed before they ship.

THE OFFLINE TEST

If the tool breaks with no internet, it depends on something it should not. We either remove the dependency or cache it properly. A tool that fails offline is a tool that fails exactly when you need it most — on a plane, in a hotel, in a meeting room with unreliable corporate wifi.

WHY MOST TOOLS FAIL THIS

They load fonts from Google. They check a remote config. They ping an analytics server before doing anything useful. Each request is a failure point on a bad connection.

We skip all of it. Fonts are system fonts. Config is local. Analytics, if any, are fire-and-forget after the tool loads.

Fast on good internet. Still works on bad internet. That is the bar.