Skip to content

Latest commit

 

History

History
125 lines (97 loc) · 6.06 KB

intermediate.md

File metadata and controls

125 lines (97 loc) · 6.06 KB

Intermediate

Table of contents

Consider All Screen Sizes

Phones

  • Always consider phone nooks
  • Use 390x844px(2.16x), 360x800(2.22x), 360x640(1.77x) wherever necessary
  • We don't design specifically for Apple/Android devices. Instead we accommodate the smallest screen sizes used by a significant number of users.

Tablets

Responsive Desktop Screens

  • Desktop: 1440x900

even if 1920x1080 is the most widely desktop screen todaywe should still be designing for 1440x900. Reason for this is that some players are playing in a smaller browser screen compared to their desktop and its a good practice to design in a small screen and make it bigger compared to designing it big and making it responsive to a smaller screen

Consider different screen sizes: https://prnt.sc/w0vSLSNHRTLk

Consider All Screen States and Scenarios

States

To know about screen states: See This

You need to think and show what happens in different screen states. some examples:

  • Disconnections
  • Page refreshing
  • Page Loading
  • Hovering
  • When the user is signed vs Guest
  • User is subscribed vs free
  • Slow internet

Scenarios

To know about scenarios: See This

Scenarios are based on the states.

Ex. Leaderboards

some samples for scenarios inside the Leaderboards are:

  • When a player clicks on a country/state/region tab
  • When a player clicks on another player details
  • When a player hovers an info icon
  • When a player scrolls up/down the list
  • When a player searches for another player in the leaderboard search bar

You should also consider edge cases such as:

  • when a player's name is too long. will it exceed the space given or cut it out?

Player Types

  • New player who doesn't know Catan
  • New player who knows Catan but not Colonist
  • New player who knows Catan & Colonist but hasn't played for a while
  • Player who plays weekly (casual)
  • Player who plays daily (hardcore)
    • These players prefer speed. Want to do stuff faster
    • These players have high familiarity and muscle memory

Questions To Ask

  • https://uxplanet.org/98-questions-ux-designers-must-ask-9b6984c6bd67?gi=66ccaed81478
  • What will this design make people do more?
  • How will it change behavior?
  • What will be the consequences of those behaviors?
  • Is that something we want?
  • What do we want players to do?
  • How often will the player use this with respect to rest of the items on the screen? Should we hide it or show it more?
  • What other parts of the app can this be used with? Should designs be done changing parts?

Note: some questions may not be applicable to certain tasks. You should be able to differentiate what is effective and what is not

Competitive Analysis

  • You should have an eye for detail when it comes to how other games do a particular feature.
  • Create a clear research format, something like this (https://prnt.sc/zHvH8tMuaQQj) and write your own insights.
  • Check https://www.gameuidatabase.com/ for a library of 500+ games to look at. Feel free to use whatever resource you have, be it using screenshot on a youtube video or you trying out the game or website itself.

Fits Colonist Artistic Style, Branding and Vision

All designs must fit Colonist artistic style. If you want to suggest a new artistic style make sure to show it separately than the UX changes.

Traverse Colonist.io to get a feel for our style.

Fits Colonist Vision & Pillars

For every element, the designer should ask why until hitting one of our Pillars or Values. If there are no pillars to direct the design decision a new pillar or guide should be suggested. No design should be subjective. All designs should be objective & scientific.

Understanding Users

Your design is probably wrong if you don't know what the user wants. Here are a few ways of understanding users.

  1. Check https://colonist.featureupvote.com for any related suggestion
  2. Post in public channels on Discord
  3. DM players who seem interested to give feedback
  4. Make a prototype and observe how testers interact with it

Polling

It's a good way to gather certain insights on users. Here is an example way of creating a poll: https://www.loom.com/share/7c891b3adb194764923bab235d9d3a0b