Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Link to dangers of shared prefs #31

Open
kurtisnelson opened this issue May 22, 2019 · 3 comments
Open

Link to dangers of shared prefs #31

kurtisnelson opened this issue May 22, 2019 · 3 comments
Assignees
@kurtisnelson
Labels
documentation
Milestone
1.0 Polish

Comments

@kurtisnelson
Copy link
Contributor

Might be worthwhile explaining or pointing to an explanation of why not use SharedPrefs

Originally posted by @jbarr21 in #25 (comment)
@kurtisnelson kurtisnelson self-assigned this May 22, 2019
@kurtisnelson kurtisnelson added this to the 1.0 Polish milestone Jul 3, 2019
@kurtisnelson
Copy link
Contributor Author

Also compare to room and SQL.

@kaushalyap
Copy link

kaushalyap commented Jan 7, 2020 •
edited
Loading

@kurtisnelson
Will this make this project obsolete? If not why?

@kurtisnelson
Copy link
Contributor Author

The AndroidX shared preferences replacement will likely be backed by SQLite. This keeps the library easy to use for new developers but has a significant performance hit both on memory and CPU. SimpleStore uses the fundamental JVM file APIs and has zero overhead until opened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kurtisnelson kurtisnelson

Labels
documentation
Projects
None yet
Milestone
1.0 Polish
Development

No branches or pull requests
2 participants
@kurtisnelson @kaushalyap