[stevage]

Fascinating. I'm really curious what the use case is that so many people seem to have. Why do you need so much data in the browser, and to be doing queries and data manipulation there? Where does the data come from? Don't you need to sync it back to a server somewhere?

[SilverRed]

It can be used as a better form of cache to make actions happen faster. So an instant messaging app for example can cache messages and stuff in a db so it does not have to refetch everything every time you switch chats.

[rattray]

This lets you write any Serious App with "single-player data" as offline-first (though yes you still need to handle syncing to the cloud somehow – jlongster has done some very cool stuff for that too, looking forward to him sharing more about that).

[stevage]

Yeah, I mean I get that in theory, I just can't think of many examples? I guess it must really be desktop apps that are delivered as web apps.

[warvstar]

We have a gaming platform where users can download and play full games in the browser. We don't use indexedDB though, we use the Cache API.

[quickthrower2]

This might be useful for a desktop-app like experience on the web. Imagine something like excel but you want to open a 100mb file and work with it right away. It can sync to the server as you are working but you just want to get working now.

Another use is privacy centric apps that send nothing to the server, using the web as a kind of “install” platform but nothing else.