colonistio / design

https://colonist.io
3 stars 0 forks source link

Mobile App: Create Room Iteration 3 #275

Open soeanski opened 1 year ago

soeanski commented 1 year ago

Goals

  1. Get users to play with friends
  2. Enable users especially with low experience levels to create a game
  3. Get users to invite friends
  4. Show users value of different maps to convert them
  5. Show users avatars of paying users to convert them
  6. Make users spend little time with game configuration
  7. Get users to customize the game

Needs

  1. Play/spend time with friends
  2. Play games with their own settings
  3. Play premium content (maps, gamemodes)
  4. Get into a game fast

Solutions

Solution 1

Create Game Flow

Conclusion

All in all I am satisfied with splitting the process into 2 parts for the lobby host.

Figma link: https://www.figma.com/proto/YiFWNF8cA06fAg34NdmqcZ/Colonist.io-Mobile?page-id=56%3A3751&node-id=56%3A3755&viewport=524%2C-26%2C0.41&scaling=min-zoom High-fidelity prototype not yet done

Considered

Reviewers

@JuanRoman77 @demiculus

JuanRoman77 commented 1 year ago

I love this :D I'd just add the rest of the names tho image

soeanski commented 1 year ago

I love this :D I'd just add the rest of the names tho

Thanks! I kind of followed Material Design here. I think adding the rest of the names is too much clutter. While dragging the handle it could be an option to show the name above the handle and only show it at the bottom once the player lets go of the handle. This way the player would know which option the handle represents without his finger occluding the name of the current option.

samgawaran commented 1 year ago

Controls from the Desktop version have to be adjusted for mobile. Dropdowns do not work as well, sliders work better.

same with Juan, I agree with this change.

Some other feedback:

I like that we have this section to show the settings: https://prnt.sc/ee-Th94vVcq1, Create Game section is nice and feels a step forward but the Lobby leaves out a lot of info so it needs more iteration.

splitting the process into 2 parts for the lobby host.

@demiculus I feel the same way with Soren here, but we would need to adjust the flow for the desktop too so there will be a longer dev time. Should we go for this one?

samgawaran commented 1 year ago

@soeanski always tag @JuanRoman77 and @demiculus as reviewer so they get notified :)

soeanski commented 1 year ago
  • Left aligned settings - I'm not sure about this, it works on a spacing sense but I believe it would be bad for right-handed users who may create their room with one hand cause the placements here a bit far: https://prnt.sc/VKfm-4WCCj69

You might be right. But then again left-side alignment ensures that players can scan the contest fast.

  • Player List (https://prnt.sc/1K-4uUEEDX5e) - This lacks information, it doesn't show Karma, game color and some other options the player has in the desktop version. Maybe we could merge our player list from my studies?
  • Chat - same with Player List, it doesn't show the clear and mute button that we have on the website

You're definitely right. The lobby part in this design needs more work. I think it is okay to leave out some information that is available on desktop (for example I intentionally left out the clear chat and mute button) but things like changing color need to be added. Maybe you could merge our two approaches and fine-tune the lobby @samgawaran ?

demiculus commented 1 year ago

There are some good ideas others have mentioned above. In general it looks off, the elemets are all over the place. Back button, title, invite placed randomly. Some left aligned some mid aligned, the length, sizes etc.. lots of things off here.

The goal & need is closer read this: https://github.com/colonistio/design/issues/274#issuecomment-1399515913


I feel the same way with Soren here, but we would need to adjust the flow for the desktop too so there will be a longer dev time. Should we go for this one?

We can go with this. We will not edit the desktop at this point. Only focus on making mobile perfect. During implementation, we'll save time by using other elements and we'll implement the perfect option later. But design the perfect option. When it comes to desktop, after we have iterated and tested the mobile UIs we will take the learnings here and make the desktop version better.

This goes for all parts of mobile.