Matchmaking Optimization - Githubissues

colonistio / design

https://colonist.io

3 stars 0 forks source link

Matchmaking Optimization #165

Closed omarhurani closed 1 year ago

omarhurani commented 1 year ago

Description

After conducting 3 tests, with results shown here:

General conclusion is:

Highest priority to optimize matchmaking is to make lobby harder to access than matchmaking games.
Next comes making matchmaking easier to access in general.
Having "Play" inside CTAs isn't worth optimizing at the moment, might explore later with improved designs.

After talking with Goku, now it makes sense to move on from testing ideas to testing designs.

From the conclusions we need (an) optimized design(s) in that direction

Related Submissions

https://github.com/colonistio/design/issues/168

References:

115

samgawaran commented 1 year ago

@omarhurani could you paste the screenshots of the prototypes you did here? thanks

omarhurani commented 1 year ago

HOMEPAGE_MATCHMAKING

Large buttons

MATCHMAKING_OPTIMIZATION

Large buttons

Small buttons, summary under

Hide lobby, show summary instead, lobby inside Play CTA

MATCHMAKING_OPTIMIZATION_2

All small buttons

Show lobby

Show lobby, add "play" to buttons

Show summary

Show summary, add "play" to buttons

samgawaran commented 1 year ago

created an implementation issue for this: https://github.com/colonistio/katan/issues/8295

closing this issue