On Wed, Feb 23, 2011 at 6:04 PM, String <[email protected]> wrote: > Mark, why do you take this position? I've found SharedPrefs to be very handy > for storing all sorts of one-off data items for which SQLite would be > overkill. Is there a downside that I'm missing?
"One-off data items" is probably OK. It's not transactional to the extent SQLite is, and it's not designed for lists or tables. There were early reports of problems due to the fact that SharedPreferences are really stored in XML, though I haven't heard a peep on that problem in probably close to a year and a half. And I have this nagging feeling that someday, something's going to happen from a UX standpoint that means non-settings stored in SharedPreferences will be an albatross. So, it's mostly paranoia, with a side order of data model ick. For the OP's roster of three booleans, as with your "one-off data items", it's probably OK. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android App Developer Books: http://commonsware.com/books -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
