How to simplify in app Application Settings management?

Question

I\'m sure every cocoa-touch programmer had to face this: I know Apple would like every application to place their settings in the Settings app. But it\'s quite limiting in w

Answer 1

If you're writing data driven applications, you could keep settings in the database, and have a single View/Controller pair that queries the DB for any settings that can be modified (each setting could be type/name/value or any other structure you could come up with).

If your data access uses a singleton, accessing the settings from anywhere in the app is simple.

Between different applications, the View/Controller used as the settings view and the database code itself wouldn't change, only the set/get performed in the different parts of the application (as well as perhaps the starting data in the DB).

Of course, if you weren't going to touch CoreData otherwise, this is a lot of overhead for settings...