"Is the idea of an offline-first web app—one that keeps running in the browser even without internet—actually a good idea?"

I’ve been experimenting with the idea of caching a web app so it continues working even when the internet drops. Apps like Google Docs already do something similar for documents. It made me wonder.

I’m a first-year college student and currently in the basic learning phase. Lately I’ve been doing a lot of “vibe coding,” and the offline idea came to my mind as something interesting to try.

So I started building a very simple task management web app.

My main goal wasn’t to build another task manager, but to experiment with an offline-first web app that still works when the internet is unstable. I focused more on the offline system than the front-end features.

What it does:

Offline-first workflow: tasks, routines, and analytics remain usable offline

Local sync queue that pushes updates to Neon/Postgres when connection returns

Productivity scoring that separates routine consistency from one-off task completion

I would really appreciate candid, critical feedback, especially on:

Offline sync edge cases I might have missed

UX friction in the dashboard/workspace flow

Whether this feels genuinely useful for daily use vs just a cool demo

If you’re into local-first apps, I would love an honest teardown of where it breaks or feels weak.

I mostly just want to know is this idea actually interesting.
github : https://github.com/ShadowXByte/TASKFLOW
vercel demo : https://tasflow.vercel.app/