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

Source: Dev.to

Overview

I’ve been experimenting with caching a web app so it continues working even when the internet drops. Apps like Google Docs already do something similar for documents, which made me wonder whether an offline‑first approach is practical for other types of apps.

I’m a first‑year college student in the basic learning phase. Lately I’ve been doing a lot of “vibe coding,” and the offline idea came to mind as something interesting to try, so I built a very simple task‑management web app.

My main goal wasn’t to create 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 on front‑end features.

Features

• Offline‑first workflow – tasks, routines, and analytics remain usable offline.
• Local sync queue – pushes updates to Neon/Postgres when the connection returns.
• Productivity scoring – separates routine consistency from one‑off task completion.

Feedback Requested

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 versus just being a cool demo.

If you’re into local‑first apps, I would love an honest teardown of where it breaks or feels weak. I mainly want to know if this idea is actually interesting.

Links

• Repository:
• Live demo: