Good ui design does take time sometimes. We should find a solution that has the most advantages and the least disadvantages. It’s also not really about “agreeing”, it’s more about real limitations.
I’ll follow this with an overview of the proposed solutions and their (dis)advantages that I could think of right now.
Goals
- It should work on different form factors (not just laptops / desktops but smartphones too).
Proposed Solutions
Idea 1: Colored decks in the deck overview (background)
This would look like this:
Advantages
- It fullfills goal #4.
- Can make it easier to understand, that some decks have something in common.
Disadvantages
- It’s unclear what they have in common (why do they have the same color, what does that mean?).
- It doesn’t fullfill goals #1, #2, #3.
- It looks a bit unappealing, or like Expertium put it:
- It increases cognitive load.
- Colors might be problematic regarding accessability, if a lot of colors need to be used.
Idea 2: Colored decks in the deck overview (text color)
This would look like this:
Advantages
- It fullfills goal #4.
- Can make it easier to understand, that some decks have something in common.
- Might look less bad than Idea 1.
Disadvantages
- It’s unclear what they have in common (why do they have the same color, what does that mean?).
- It doesn’t fullfill goals #1, #2, #3.
- Doesn’t work for all colors (e.g. yellow).
- Might not work when a lot of presets are beeing used (colors need to be readable enough for accessibility as well).
- It slightly increases cognitive load.
Idea 3: Make it toggle-able, e.g. in “view → show preset colors” or similiar
Advantages
- It fullfills goal #4.
- It doesn’t distract from the relevant info (except if the user chooses to toggle it on) → no cognitive load, unless explicitly set by user.
Disadvantages
- It’s unclear what they have in common (why do they have the same color, what does that mean?).
- It doesn’t fullfill goals #1, #2, #3.
- Doesn’t work for all colors (e.g. yellow).
- Might not work when a lot of presets are beeing used (colors need to be readable enough for accessibility as well).
- Low discoverability.
Idea 4: Options screen could be a split view, with the options on the left and the preset preview on the right (differently colored for all presets)
This would look like this:
Advantages
- Maybe fullfills goal #1, though I’m not exactly convinced.
- Fullfills goals #2, #3.
- It only shows in the preferences, where the user would actually change presets.
- It might
Disadvantages
- Does not fullfill goal #4, since the options screen doesn’t have enough space on mobile devices.
- Might not work when a lot of presets are beeing used (too many colors, potentiall problem with accessability).
- Might be a distraction when you’re editing something else in the deck options, like FSRS parameters.
Idea 5: Options screen could be a split view, with the options on the left and the preset preview on the right (only one color for the currently displayed preset)
Advantages
- Maybe fullfills goal #1, though I’m not exactly convinced.
- Fullfills goals #2, #3.
- It only shows in the preferences, where the user would actually change presets.
- It might
- Doesn’t have the issue with multiple colors if a lot of presets are being used.
Disadvantages
- Does not fullfill goal #4, since the options screen doesn’t have enough space on mobile devices.
- Might be a distraction when you’re editing something else in the deck options, like FSRS parameters.
Idea 6: Add a preset column to the deck overview
This would look like this (though keep in mind that this picture is from an addon and has much more than was proposed in this idea):
Advantages
- Fullfills goals #1 and #2.
- Might be easier to implement.
Disadvantages
- Doesn’t fullfill goal #3, but at least you could easily spot your mistake after editing the deck options.
- Doesn’t fullfill goal #4, as there wouldn’t be enough screen real estate.
- It increases cognitive load.
Idea 7: Show presets in the deck overview when a button is pressed (e.g. shift)
This would look like this:
Advantages
- Fullfills goals #1 and #2.
- Doesn’t always show, thus doesn’t increase cognitve load.
Disadvantages
- Doesn’t fullfill goal #3, but at least you could easily spot your mistake after editing the deck options.
- Doesn’t fullfill goal #4. The screen real estate might still be a problem. The biggest problem is the lack of an available keyboard.
- Low discoverability.
What now?
We need to find theoretical solutions to the disadvantages of at least one of the proposed solutions above. Especially the goals must be met.