openmultiplayer / openmultiplayer/launcher

UX suggestions

Open
#56 1 comment 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
203
Forks
97
PR merge metrics
No merged PRs in 30d

Description

1) Lock Server Icon (Colors):

  • The current dark icon for a locked server might be misleading for user experience. The dark gray color could suggest that the server is down or that there's an issue with the IP address. I propose adding a third state, a "no info" state, where the icon is dark with a distinct design from the unlocked and open icons. For the locked server, the icon could be red, and for the unlocked and open states, it could be green (as it is currently).

2) Hover State Application-wide:

  • The application lacks a consistent hover state. Currently, hovering only changes the cursor to a pointer. I suggest enhancing the hover experience by incorporating changes in background colors. Currently, the hover effect is only present when hovering over a server item in the server list.

3) Light Mode Color Adjustment:

  • While dark mode is popular, especially among gamers, having a well-thought-out light mode can enhance user experience. In light mode, the current light gray color appears too bright. I recommend adjusting it to a darker shade for improved visibility.

4) Settings Modal:

  • The use of purple as the primary color in the OMP Launcher might be too visually overwhelming in the settings modal. When opening settings, there are three buttons with the primary color and one danger button, which feels too aggressive. Additionally, the Languages section contains many checkboxes, but only one can be selected. Consider using an HTML select element to allow users to choose a single option, providing a more user-friendly experience.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing server list hover behavior and the settings modal, then compare the four UX proposals as separate pieces of work. Clarify which icon states, application-wide hover treatment, light-mode color adjustment, and language-selection control are accepted before changing anything. Done means the agreed UX changes are implemented consistently and the resulting interactions are visually distinguishable.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.