Have You Ever Used a Website That Keeps Working After You Turn Off Your Internet?

#webdev #programming #productivity

Neither had I. So I built one.

Most websites die the moment your internet does. You lose signal, you get a blank screen or a spinner that never stops. Refresh the page offline and it's gone. That's just "how the web works," right?

I refused to accept that.

I'm a Front-End Engineer based in Lagos, Nigeria. If you've ever tried to use a web app on a bus in Lagos with 2G cutting in and out, you understand why I started thinking about this differently. The network isn't reliable. But the app should be.

So I built an architecture I call Browser Physics.

What Is Browser Physics?

Browser Physics is my answer to one question: what if the browser didn't need the internet at all?

I treat the browser as a self-sustaining operating system and the network as an optional backup, not a requirement.

Instead of fetching data from the server every time a user navigates, I built a three-tier storage model:

Hot Data — Zustand in memory. Page transitions take zero milliseconds because they read from RAM, not the network.

Warm Data — IndexedDB on disk. Survives hard refresh. The app boots from local disk even with no internet.

Cold Data — Supabase, the actual database. Only consulted on first boot and when the user reconnects after being offline.

On top of that, a Service Worker intercepts network requests so when you navigate around with no internet, everything is served from local cache instantly. No spinner. No broken state. Same speed as online.

When you're back online, WebSocket pushes live updates the moment data changes in the database. When you reconnect after being offline, an automatic revalidation fetch runs and syncs only what changed so you always have the latest data.

See It Live

I am currently building TSWorldTech, the first real production platform running Browser Physics.

tsworldtech.com

The application is currently 85% complete. Data, navigation, real-time sync, and offline resilience are all working. Image offline persistence is the remaining layer in active development.

Here is the challenge:

Visit the website while online. Then turn off your data. Navigate around. Refresh the page. It all still works, same speed, same data, zero spinners.

Then come back and tell me what you see.

Would You Like to Know How I Built It?

I am planning a full technical breakdown covering the Service Worker architecture, the three-tier storage model, the HydrationGate pattern, the WebSocket and IDB reconnection sync, and every decision behind each layer.

If that is something you would want to read, drop a comment below. The more interest, the sooner I write it.

I am Abdullah Teslim, a Front-End Engineer and the person who got tired of spinners.