> On Jul 30, 2015, at 1:56 AM, Woof <[email protected]> wrote:
>
> IndexedDB isn't currently (AFAIK) using persistent storage, so will be purged
> at some point. In use though I haven't seen this happen unless I've cleared
> the data myself. I did try using the persistent storage with the FileSystem
> API but I found the quota request was putting users off (a big scary pop-up
> from the browser, which users were declining).
>
This is a little off topic but …
The above is a fairly typical developer reaction to browser’s popping requests
for permission. The implication being that they wish there wasn’t a pop-up.
Developers can remove the “scary” part by, raising a message box themselves
before executing the call that pops up the browser permission request. In this
message box they can explain why the application needs the permission. In this
case it would explain what data is going to be saved in persistent storage and
the benefit of doing do. Doing this will greatly improve the chances of your
user giving permission.
At least browsers request permissions one by one so applications can provide
explanations before the request appears. This is not possible with Android’s
completely broken all-or-nothing permission system.
Regards
-Mark
--
You received this message because you are subscribed to the Google Groups
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
