Settings are options that provide users with control over certain features in your application (for example, the ability to turn sound on or off in a game). Since settings can be overwhelming to users, you should try to minimize the number of settings that you provide. So how do you decide whether you should make something a setting?

Where should I put the setting?

Allow users to access settings from the application menu that appears when users swipe down from the top of the screen. Include a Settings icon in the top right position of the application menu.

How should I organize settings?

  • Position the most frequently used or most important settings first. This approach helps make it easier for users to change settings quickly.
  • Try to group related settings together. Use headings and dividers as a way to distinguish groups of settings. If there are no logical relationships among settings, then try to organize the items by component type (for example, keep toggle switches together and check boxes together).
  • Allow users to access more advanced features through progressive disclosure (for example, you might show a few basic settings before revealing more advanced features on a second screen). If there are dependencies with other fields, try to 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, only allow users to drill down a maximum of two levels.
  • Include a title bar and an action bar on the Settings screen. The action bar should include a Back button that allows users to navigate.

What else should I consider?

  • Save changes implicitly.
  • Allow users to search for settings. Be sure to register each setting so that they can be included in search results. Include additional, meaningful search terms (for example, include synonyms for the setting).

Was this information helpful? Send us your comments.