We are thinking of making PageStorage into a persistent storage of this kind.

@Hixie sometimes there is need of "cross-page" storage, and PageStorage is bound to some navigation point (page) if I understand it correctly. Would be nice to have some persistent global app storage, not just for page, like LocalStorage for web apps.

@mit-mit, would also support including this as an out of the box plugin in the MVP. Anyone implementing any app with some sort of login (probably a large share of the market) will need this and the alternative (spinning their own) is a lot of non-trivial non-value-add code.

This is a frequently requested plugin. :) Posse just asked if we had one.

We have a working, pure dart concept for this if you are interested. The only thing that it doesn't cover (out of scope for us) was encryption of the values (similar to secure storage on NSUserDefaults & SharedPreferences). I would think that for that protection level you'd want to fallback to a plugin.

There are other "platform-integration" aspects of sitting on top of NSUserDefaults and SharedPreferences in terms of behaving correctly with regards to preference synchronization, etc.

Supporting some synergies with preferences cloud functions would indeed be really cool
https://developer.android.com/guide/topics/data/autobackup.html
https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/UserDefaults/StoringPreferenceDatainiCloud/StoringPreferenceDatainiCloud.html

We got another request for this today. I believe we may have some SharedPreferences/NSUserDefaults code from internal Flutter customers we could share here. I've asked @collinjackson to investigate.

Try this: https://github.com/lakexyde/flutter_localstorage. Just needed a simple way to store key-value, so I created this.
Hope you find it helpful.

Try this: https://github.com/lakexyde/flutter_localstorage. Just needed a simple way to store key-value, so I created this.
Hope you find it helpful.

looks promising. thanks for your effort

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.