Closed samgawaran closed 1 year ago
Overall I like solution 1A the most. I think you used the available space much better than previous iterations did while keeping things relatively clear and ensuring usability of most elements. Some things have to be adjusted.
Here are some of my thoughts:
Overall
Some smaller UI element issues: Game Creation Context
Room/Lobby Context
Forgot to write my answers on the feedback from before and in here: https://github.com/colonistio/design/issues/274#issuecomment-1399423599
Remove the trash and volume icon in the chatbar
I can't, it's the option that we allow on the desktop. unless we remove those then this one should also have that ability also.
Ignoring Add Bot for Host
same as above, host have that option so it should also be shown in the mockup here
besides that, I'd adjusted all of the solutions above based on that prior feedback
======== https://github.com/colonistio/design/issues/280#issuecomment-1401549936
How do you remove players from a lobby as host?
same implementation in desktop, after we decided on a solution, I'll do the iOS sizes and these scenarios
Feedbacks why Solution 1A is better
Good idea, in a sense, I would say solution 1A is more UX-friendly compared to Solution 2, but I think this solution, makes it easier for players to start the game due to lesser clicks, I'm okay with all of the solutions though so let me know what route we're going for @demiculus
Game Creation Context
Preview
is in the current implementation for MapsScrollbar ending randomly
I get what you mean but I find it hard to focus on the scrollbar for the mockup so I just used what the existing is on the desktop. and if you check the prototype than you'll find that its actually scrollable. Slider text should be left aligned
I disagree, I think its more important that there's no empty space on that side as to have balance. Room/Lobby Context
Elements inside the room need some corner radius, looks a bit strict/harsh, not enough like a game
is this for the player list? it has a 4px corner radius, I think going for a bit more will make it off-brand on the desktop version.
We should use ifferent font weights or sizes in the chat window to differentiate between player and chat message
- I agree, maybe making it all player details on bold will make it look better.
active state of the segmented button (Settings/Players) could be more obvious
- thats the current implementation on Desktop, we shouldn't stray too far away from it. We can however propose a change on how it will look in the future
on all other comments, I agree
Goals
Main
Sub
Needs
Both on Room Lobby/Settings
Principles
Consistency Efficiency Visibility of system status User Control and Freedom
Research
Research is done here: https://github.com/colonistio/design/issues/274
Solutions
Solution 1A: 2-Step Create Room
Prototype Link: https://www.figma.com/proto/4sPdkWQrqoiGgFkMLtVSqr/Colonist-UI%2FUX-App?page-id=442%3A62785&node-id=818%3A107513&viewport=-6808%2C-5364%2C0.25&scaling=min-zoom&starting-point-node-id=818%3A107513
Followed Principles: User Control and Freedom, Visibility of System Status Ignored Principles: Consistency (Website)
Get Ready
Player list
- adjusted this one from the original my previous iteration, only reason why I did the long playerlist is to consider long player names like WWWWWWWWWWW, but how many players have names like that? it doesn't make sense to sacrifice the UI for a small minority of players. and with these design, we can fit 2 players in a single rowSolution 1B: - 2-Step Create Room
Followed Principles: User Control and Freedom, Visibility of System Status Ignored Principles: Consistency (Website)
Solution 2: - Slide Up/Down Playerlist Slider
Followed Principles: User Control and Freedom, Visibility of System Status, Efficiency Ignored Principles: Consistency (Website)
Conclusion
Proposed Solution:
Solution 2: - Slide Up/Down Slider
Benefits:
Potential Risks:
Considered
Reviewers
@demiculus @JuanRoman77 @woodifred @5econds