Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In a recent version, forge.prefs was introduced. This feature seems very similar to the localStorage API except that forge.prefs accepts callbacks.
What is the advantage of using one over the other? What are the differences in operation?
The implementation of forge.prefs uses the device’s native storage implementation, for example NSUserDefaults on iOS and SharedPreferences on Android.
The exact ramifications of this depends on the platform, but the main goal here is increased upper limits on the amount of storage – some devices also don’t have persistent localStorage by default IIRC…