App with optional modules - main settings menu naming?

Question

Our app has multiple products that you can opt into, let's pretend it's named "Xanadont". Each product (or module) has configurable settings plus the main app has settings. There's a settings view called "Modules". The left column lists each module. The right column is the details view of the settings per the selected module.

The question is what to name the main settings list entry? We have two camps: 1 - label it "General", 2 - label it "Xanadont" (the app's name). Here's a rough mockup.

General Camp

• What's being configured is not a module, therefore labeling it the app's name is not appropriate.
• "General" would be less confusing.
• "Generel" (or Global) seems to be the industry standard.
• No real-world precedence in other software for a menu labeled as the app's name.

Xanadont Camp

• What's being configured is kind of a module, it's the "main" module.
• Users won't be confused; it should be obvious for what use the section "Xanadont" is.
• It promotes the app's brand.
• "General" is cliché, "Xanadont" is more evocative.

So ... what do you think?

Edit - the "main" settings area can have settings that affect the modules, but other settings may not. An example would be Date / Time and number formatting.

Answer 1

It may already be too late for this, but I would manage your settings structure differently altogether. That is, make the various module settings only available to users when they're within the various modules, rather than at some top level.

At the top level you could just label settings as "Settings" and then within each of the modules you could denote the internal settings with a recognisable icon.

But, assuming that isn't possible...

I think you most definitely don't name it "Xanadont" or whatever the app is called. The only way you'd get away with that would be to call it something like "Xanadont Settings", but that probably isn't ideal.

The main reason for not just using the App name is that it's likely to lead to confusion. Even going by your question, one side is saying that using 'General' would be "less confusing", while the opposing view is that using the App's name means that "users won't be confused".

'General' actually sounds like a fairly good option (even Apple uses it within their iOS settings). While some may argue that "General" is cliché, that's actually not a bad thing when it comes to user expectations and the overall user experience. So I would opt for General.

But there are other options. Here's a few (not in any particular order):

• Settings (listed first under the main Settings screen is enough to denote that its referring to overall settings, especially since the other items in the list are the various module names within the app).
• Main Settings
• Main
• App Wide
• Overall
• Generic
• Miscellaneous
• Various
• Other