Even though Apple recommends it, placing preferences in their Settings.app is currently probably not a good idea. The list of applications in Settings.app quickly becomes unmanageable, and people don't look for settings in there. In the bjango article, Russell Ivanovic from ShiftyJelly explains:
We received several emails a week from people asking for features that were already part of our application.
The best advice I can give at the moment is to get rid of settings altogether.
I think the best solution at the moment is this:
- If you can at all avoid them, don't offer preferences.
- If you absolutely need to offer preferences, put them into your app. The bjango article has examples of how to best do that, and even offers free artwork you can use for settings buttons.
I'm using "preferences" and "settings" interchangeably, although John Gruber is correct in pointing out that they are called "settings" on the iPhone, and "preferences" on the Mac (Windows seems to use both terms, as well as "options"). He also writes: "Settings are often unavoidable â€” things like usernames and passwords for online services must be adjustable." Usernames and passwords are great examples of settings that can easily be exposed within the application itself without even creating a "section" for settings; for example, you can ask the user to enter a username and password when he starts the application for the first time, or after manually logging out, or when he creates a new account, or when he changes an account. ↩︎
If you require a short url to link to this article, please use http://ignco.de/211