title: How long is too long for storing data in Android SharedPreferences?
body: <p>I have looked up a lot about the different data storage methods, and am trying to figure out at what point Android SharedPreferences is not right.</p>
  
  <p>I realize the limitation of a string is quite colossal (~2B), so storing it isn't a problem memory-wise, I'm more curious about "Best Practice."</p>
  
  <p>I will have somewhere between 5 and 15 "Updates" that I will have over the life of this app. I would like each phone to save these updates. An update will have a short title, and be anywhere from a sentence to two paragraphs.</p>
  
  <p>I realize there is usually a concern of extensability, but there is no concern for that here. It is an app used yearly for 1 weekend.</p>
  
  <p>I need no search or manipulation to these, just the ability to store them.</p>
  
  <p>I could use GSON to store them all as a JSON object, but is that just too big of a string for preferences? Or is it fine because internal storage (as a CSV or something) or a database would be overkill?</p>