The change of YES/NO buttons

[eveneme]

Changing the YES/NO buttons to a more modern button slider.

Before:

After:

[TheBrambleShark]

While I'm not very experienced with development in this particular domain (i.e., WoltLab, PHP), my experience developing UI/UX components for WPF/WinUI says that you'll need to provide additional information, specifically:

1. Where should this change be made? What components can be upgraded, where do these fields appear?
2. Why is the current design negatively affecting user experience?
3. How does the new design positively effect user experience?
   1. Does the new design solve any problems, e.g. with ambiguity/intent, comfort, or accessibility?
   2. What advantages does the new design have over the old design?
4. What are potential drawbacks to adopting this new design?
   1. Are there areas where we may adversely affect understanding of a particular prompt?
   2. Does this new design introduce issues with comfort/ease of use/accessibility?
   3. What downstream effects might this have, such as requiring the reprhasing/re-translating of prompts?
      • "Have you read and agreed to the Terms and Conditions?" makes sense with Yes/No. A slider may be less clear what is meant here without rephrasing the question to something like "I have read and agree to the terms and Conditions."
      • Is the cost of downstream effects worth the benefits brought to us by the new design?

Ultimately I'm not the decision maker here, but I wanted to provide my $0.02 and anticipate some questions the others may have.

[eveneme]

Have you used WoltLab? It's about replacing buttons in every section, primarily in the administrative panel, with a more modern button that is already used practically everywhere.

[cls-design]

I don't really see any advantage in changing this and I don't think that such a switch is more modern. I prefer to have a clearly labeled button. You are also ignoring the fact that there is a third status in this context:

[cadeyrn]

Supposedly modern does not mean better. This proposal has no advantage at all. I also prefer the current implementation.

(It's a bit strange to give yourself a thumbs up for your own suggestion.)

[eveneme]

Just take a look at the up-to-date pages and new components like mui or tailwind, and the matter becomes clear, whereas WoltLab, in many aspects, doesn't look fresh and probably won't change quickly. How do you think what button would WoltLab use if the engine was created in 2024?

[TheBrambleShark]

While I agree there are cases where a slider may be more appropriate (particularly when the question it is answering is worded as a yes/no question), but I strongly disagree with the suggestion that a slider is more appropriate in all cases or that it should be treated as a drop-in replacement.

From a technical side, a slider is a visual abstraction of a checkbox and as such should only be used in cases where it could be backed by (read: replaced with) a checkbox and no functionality would be lost.

Perhaps instead of replacing anything, we simply add the slider as a control that can be used by plugin developers.

[aethior]

First of all, although we all probably already know it, I will point out that this object is called "toggle button" or "toggle switches". This will make it easier to unify terms and future searches.

1. Toggle buttons are a "modern" (or visually more attractive) solution.
2. Toggle buttons can be used with colors and words that help to understand them.
3. Toggle buttons can be made with three states.

But...

1. Toggle buttons must represent a direct action. They are intended so that the user does not have to save the changes afterwards. Is this a feature we want in the ACP? Are we sure that any changes should have a direct impact on user permissions (without a final check)?
2. Are we sure that toggle buttons are the best solution in an Admin Panel full of buttons that can be clicked unintentionally when scrolling?

More info: Toggle switch design: the full run through

---

I like many of the visual proposals you are making, but I think you have to bear in mind that they are not going to be implemented before version 7.0.

In my experience WoltLab maintains aesthetic consistency in minor versions (6.x) and makes major changes in major versions (7.0). If you make this kind of suggestions you should think about a complete view of the software. If you make such suggestions, you should think about the software as a whole, not small suggestions that might not fit together in the future.