My intended joke was that supporting a mobile experience would lead to not using the large amounts of horizontal space available on most desktops, thus blaming the lack of use of horizontal space on mobile UI
Sorry Iām just unfamiliar with UI constraints. It doesnāt seem intuitive that you could not use the full space available on desktop, while proposing a different UI for mobile usersā¦
In any case, I do think this is becoming an issue, and even more now that we added a new columnā¦ (even though I like the idea of displaying handicap).
Iām not saying itās impossible to fix, Iām saying that looking good on all possible screensizes, particularly ones as radically different as desktops (normally landscape and quite large) and phones (normally portrait and quite small) is infamously difficult, and having this sort of trouble with the desktop version and then blaming Mobile UI is exactly the sort of insane troll logic that can plausibly be shown to be correct over which Dan would swear revenge
Itās true, a narrower component is easier to adapt to Mobile. But this table has hardly been optimized for mobile
What do you mean? It looks ideal
The reason I suggested right aligning is so that when there are single digit handicaps and double digit handicaps, the āonesā column lines up in the display. This makes it easier to read a column of numbers.
If the vast majority of player pages donāt contain a mix of single and double digit handicaps, centering everything seems like it could be the simplest and most aesthetic solution for the vast majority of user pages.
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.