3 ms·
Ask HN: Effective organization of settings in UX design
Quick question about UX Design, pertaining to Settings management in applications --
Is it preferable to keep settings with the things they are related to? Or aggregate them in one "settings" panel? Or, is a hybrid the best approach (keep all the settings with their related areas, but also keep an aggregation of the settings somewhere as a "master" settings list)
An example to illustrate -- Let's say I'm building a RSS feed reader app (I'm not, promise) -- and I want people to be able to let's say, subscribe to some RSS feeds. Now, I have a menu item on the top navigation bar that deals with Feeds (essentially, containing all the actions you can do that are related to "feeds"), so I can put an option like "manage subscriptions" there, and it will make sense.
HOWEVER, I also have a settings button on the top navigation bar -- Which arguably should also be able to manage subscriptions (as the things you are subscribed to could be considered settings)... So should I duplicate those other settings there?
If I lean in the direction of keeping the settings in their respective contexts, it seems to increase complexity. However, if I keep the settings in a big settings list, then it's just overwhelming/tiresome. And even if I duplicate the information, UX Fragmentation is something I don't want to do (at least on the surface, increasing the places to which UX changes must propogate seems like a terrible idea).
I'm probably asking in the wrong place, but if anyone's got some thoughts, I'd like to hear it -- I'm currently leaning towards context-based settings (the downside of which is the user has to go to the context area for whatever they're trying to do to access settings)