Skip to content

[Feature]: Redesign options UI for natural UX flow #124

@Xerrion

Description

@Xerrion

Problem

The current options UI feels unintuitive and disorganized. Settings are scattered across tabs in ways that don't match how users think about them, labels aren't self-explanatory, and related options aren't always grouped together. The overall experience doesn't feel polished or natural to navigate.

Proposed Solution

Audit and redesign the options layout with these principles:

  • Group by intent, not by implementation - settings that affect the same thing should be near each other
  • Progressive disclosure - advanced/rarely-changed options should be secondary; the most-used controls (enable, lock, test) should be immediately visible
  • Consistent language - option labels should describe the outcome, not the mechanism
  • Logical tab structure - tabs should map to distinct user goals ("Roll Frame", "Loot Window", "Appearance", "Notifications", "History") not internal module names
  • Contextual enable/disable - dependent options should be visually disabled when their parent toggle is off
  • Better section headers - sections within tabs should have clear purpose-driven titles

Areas to Audit

  • Layout section in the Loot Roll tab is overloaded - timer bar options, icon position, text layout, and frame sizing are all mixed together
  • Appearance tab has background, border, font, and icon size in four separate sections but no clear hierarchy of importance
  • History tab could benefit from clearer grouping of what triggers recording vs what triggers display
  • Notifications tab sub-options (your rolls, group rolls) should have better visual indication of their dependency on the parent toggle

Acceptance Criteria

  • Tab names reflect user goals, not internal module names
  • Each section has a single clear purpose
  • Dependent options are disabled (not hidden) when their controlling toggle is off
  • Most-used controls are at the top of each section
  • Option labels are written in user-facing language, not developer language
  • No breaking changes to config key names or defaults (purely presentation/layout)

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-ConfigOptions table, config window, AceDBC-UsabilityUX improvement, better defaults, polishD-ComplexMultiple files or systems involvedP-All-VersionsAffects all supported WoW versions

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions