Simply storing the data in IndexedDB should solve the problem. The user can get at the data there too, but it's a whole lot more complicated. Complicated enough that most users won't do it.
There's no way to make it completely impossible for the user to access the data. Doing that is exactly what DRM tries to do. It's a painful process and it never works out well, for neither the user nor the developer. / Jonas On Fri, Dec 6, 2013 at 5:10 AM, <[email protected]> wrote: > Hi, > > I'm wondering how I would be able to download and store an add-on package for > an app. As an example let's assume I would want to make a wordlist app and I > want to download an extra wordlist. > > It seems like I can use the WebPayments API and handle the download of the > add-on through the server-side component needed to handle the payment. What I > don't understand is how I can store the add-on on my device. When my app is > privileged I can still not store the add-on in my app folder, only on the SD > card. > > How would I now prevent my users from copying the data between SD cards? I > could probably do a request to my server component containing the data in > navigator.id to verify that the current user has bought the add-on. This > would however make it impossible to use the add-on content in the app > offline, since I cannot verify if the content was bought. > > Am I missing something, or is this how it works? > > Thanks in advance, > > Casper > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
