Ask HN: Requiring browser cache / IndexedDB for SaaS app?

3 points by truetraveller ↗ HN
I'm developing a desktop SaaS app that relies heavily on local browser caching, using IndexedDB. This is to reduce server load. This is a part of the business strategy.

I am making IndexedDB a requirement to use the app. IndexedDB is available on 97% of all browsers. If IndexedDB support is not found, I will show a popup.

Is this reasonable? Do you thinks users would make a fuss? Are there any corporate policies that disable the local cache, or clear it when the browser closes?

4 comments

[ 2.7 ms ] story [ 18.2 ms ] thread
I don’t see a problem with this - but have a think what the outcome is for the user if they don’t have it. Can they use the app without local cache? Is there functionality impacted? I’d suggest looking into localForage instead of indexeddb directly I found it easier.

Edit: also maybe look into private mode (incognito) as that probably clears cache on exit