Do you know what your app actually does when the internet is bad?

by•

I tested one of my projects on a train last week, on patchy 3G that kept dropping in and out, and honestly it was a disaster. Spinners that never stopped. A form that said “Saved!” but hadn’t actually saved anything. A button I tapped three times that created three duplicate entries. And one screen just went blank with no error at all...

On my laptop with fast wifi it’s perfect, so I never saw any of this. I just assumed if it works for me, it works.

I think this is a really ignored gap. Most of us build and test on fast connections and good devices, then ship to people on weak signal, cheap phones, or data saver mode. Nobody complains, they just close the tab. And a huge chunk of real users are on slow networks, especially outside big cities. You’d never see it in analytics either, it just looks like people bouncing...

What I changed after that:

  • Throttled my network to “Slow 3G” in Chrome DevTools and clicked through every main flow

  • Added proper loading, error and retry states instead of infinite spinners

  • Disabled buttons after the first click so slow responses don’t create duplicate submissions

  • Only show “Saved” after the server confirms it

  • Set sensible timeouts, so a request fails clearly instead of hanging forever

Still not sure how far to go with offline support for a small project. Full offline mode feels like a lot of work, but the basics seem like the minimum...

Do you test on slow networks at all, or just on your own fast connection..? Has a bug ever only shown up for users on bad signal..? And do you have any good tools or habits for catching this early..?

5 views

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.