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?
Just use NSUserDefaults, that is what it is there for. Why do you feel like you have too many for it?
Also, if you decide to use the settings bundle later, you’ll need to use NSUserDefaults anyway.