Author: Roy Tian
In this tutorial, we’ll go over Application Data, File API , HTML5 Web Storage, Indexed Database API and remote data access. With these you can store more data – and store it more efficiently.
Application Data, when an app is installed, the system gives it its own per-user data stores for application data such as settings and files. You don't need to know where or how this data exists, because the system is responsible for managing the physical storage. Just use the application data API, which makes it easy for you to work with your application data.
Persistent data that exists only on the current device
Data that exists on all devices on which the user has installed the app
Data that could be removed by the system at any time
File API, you could save app data directly in file. Windows Store App supports accessing files at local temp directory, local storage directory, and system well-known directories.
Get a StorageFolder which you can load data from files in your app package
Windows.Storage.ApplicationData.current.localFolder, roamingFolder and temporaryFolder
Provide StorageFolder objects for your app data locations
Windows.Storage.Pickers.FolderPicker,FileOpenPicker and FileSavePicker
Provide StorageFolder objects for the Pictures, Music, Videos, and Documents libraries, as well as Removable Storage.
Provide a createFolderAsync method which you can obtain a StorageFolder in that location
Return a StorageFolder for a given pathname only if your app already has permissions to access it
Storing key-value pairs on the client side
IndexedDB has a 250MB limit per app and an overall system limit of 375MB on drives smaller than 30GB, or 4% (to a maximum 20GB) for drives over 30GB
Carrying out multiple transactions in different windows at the same time
IndexedDB on Windows 8 has no complex key paths—that is, it does not presently support multiple values for a key or index
Storage spans multiple windows
Can't store a larger amount of data, recommends a limit of 5 MB
Remote Data Access: