Settings are options that give users control over certain features in your app (for example, turning sound on or off in a game). Since settings can be overwhelming to users, try to minimize the number of settings that you provide.

Do I need a setting?

Diagram demonstrating that when 80% of your users have the same preference, you don't need a setting.

Where should I include settings?

Include settings on the application menu that appears when users swipe down from the top of the screen. Place a Settings icon in the top-right corner of the application menu.

How should I organize settings?

Position the most frequently used or most important settings first to make it easier for users to change settings quickly.

Group related settings together. Use headings and dividers to distinguish groups of settings. If there are no logical relationships among settings, try to organize them by component type (for example, keep toggle switches together and check boxes together).

Let users access advanced features through progressive disclosure (for example, show a few basic settings before revealing more advanced features on a second screen). If there are dependencies with other fields, position the dependent fields after the controlling field.

Keep the hierarchy of settings as flat as possible. If you need to organize the settings into categories, let users drill down only two levels.

Include a title bar and an action bar on the Settings screen. The action bar should also include a Back button that allows users to return to the previous screen.

Device showing a list of notification settings.

What else should I consider?

Save changes implicitly.

Let users search for settings. Register each setting with the search framework so that they can be included in search results. Include additional meaningful search terms (for example, synonyms for the setting).

Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus