4 ms·
yeah I gave up on the direct API, I used Dexie for my product. I think it's funny you say a problem is that it's async while another commentor says a problem i
by NelsonMinar 2y ago
yeah I gave up on the direct API, I used Dexie for my product.
I think it's funny you say a problem is that it's async while another commentor says a problem is it blocks the UI. Maybe it's the worst of both?
- fastball 2y agoYes, it's the worst of both. Dexie is at the mercy of the aforementioned issues with IDB (differing browser implementations, blocking of the main thread, hard to debug, can't actually guarantee persistence beyond "best effort"). The issues are much more prevalent on mobile browsers in our experience (iOS Safari in particular being the worst), to the point I think we'll need to move off it for our persistence layer in our own app and will unfortunately be forced to require our users to download wrapped apps (Capacitor and Electron) if they want offline persistence guarantees. But yes, the Dexie API is indeed a much better experience for working with IDB.