Most Efficient Alternative Method of Storing Settings for iPhone Apps

Posted by JPK on Stack Overflow See other posts from Stack Overflow or by JPK
Published on 2012-03-22T04:16:54Z Indexed on 2012/03/22 5:29 UTC
Read the original article Hit count: 282

I am not using the Settings bundle to store the settings for my app, as I prefer to allow the user to access the settings within the app (they may be changed fairly often). I do realize that there is the option to do both, but for now, I am trying to find the most optimal place to store the settings within the app.

I have a good number of settings (from what I have read, probably too many for NSUserDefaults), and the two main options I am considering are: 1) storing the settings in a dictionary in the plist, loading the settings into a NSDictionary property in the app delegate and accessing them via the sharedDelegate 2) storing the settings in a Core Data entity (1 row on Settings entity), loading the settings into a Settings object in the app delegate and accessing them via the sharedDelegate

Of these two, which would be the optimal method, performance wise?

© Stack Overflow or respective owner

Related posts about optimization

Related posts about core-data