On 5 December 2013 02:46, Ralph Versteegen <[email protected]> wrote: > On 4 December 2013 19:20, Keith Gable <[email protected]> wrote: >> You should use the Play APIs for anything related to in app purchases. Best >> practice is usually to check they're authorized every time they're connected >> when they start the app. > > Why? In case they purchase it from another device? Or to prevent > config file editing? > >> You can store anything on the storage card and it will persist. Only the app >> folder (/data/data/com.you.game usually) gets deleted on uninstall. > > So here by storage card you mean just completely unorganised storage? > > I wanted some form of private storage, since that seemed sensible for > storing purchase data. But if we're not worried about someone plugging > their phone into their computer and simply opening and editing the > relevant file with RELOADSpy (or possibly uploading it), then well > obvious we're not worried about anything.
But if purchases are checked on every run on the store (Play or Ouya or whatever) as well as cached in a file, then of course there's no need for persistence across uninstalls. > I think the way of storing private persistent data I was thinking of > is "Shared Preferences" > https://developer.android.com/guide/topics/data/data-storage.html#pref > however it doesn't explicitly say it's not deleted on uninstall. > >> Note that many devices don't distinguish in the UI the storage card and the >> /data/data partition. In Android 2.x, the storage card was usually /sdcard. >> I forget what it is on 4.x. > > What do you mean by UI? _______________________________________________ Ohrrpgce mailing list [email protected] http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
