...
Kevin views the details of the game created by George Karl. He can see the location and time as well as a map of where the court is. The average skill level is indicated by a bar graphic and the first five players are shown by their profile pic icons. We can sort the list of currently added players so that the five most relevant players are shown to Kevin. Now that Kevin is registered and logged in, he can see his profile pic on the left along with a logout icon. Kevin clicks the Join button to add himself to the game. He now appears on the game roster and the time has been slotted into his schedule.
The boxes on the home page make the games very visible. Given that the core functionality of the site is to connect players with games that they would be interested in, this design decision makes sense. The parameters are laid out logically to enable good learnability. If we use javascript on the filter selections, then the user would be able to figure out the implications of each option with great immediacy. However, some efficiency is sacrificed with the design. Many games cannot be viewed at once when the games take up large screen area. It wouldn't make sense from a speed standpoint to load all available games at once so a button must be clicked to display additional games. An expert user might rather have a large list of games without the box interface to assimilate more information quickly. The drop downs on the time option and the slide bars on the skill range will help limit error prevention. If we can implement a standard list of valid locations we can also do some error prevention on the location criterion.