Community Sports App Case Study

Yashwanth Kotha
5 min readFeb 17, 2020

Community Sports App Case Study

Problem Statement

  1. People who want to play games in the community but never seem to find an empty slot without going and checking out the venue physically.
  2. The person has no knowledge of the venues, facilities, and their rules.
  3. Finding players to play within your community.

Solution

CSA is an app that specializes in booking sports venues. The app makes it easier to find the venues, book a slot for playing in the court, invite friends for a game, etc. The app also has a feature where the users can use a 360° walkthrough inside the venue

  1. CSA makes it easier to find friends who have similar interests in sports as them.
  2. It has an option to book a slot at any sports venue up to 3 days in advance.
  3. The users can use the 360° walkthrough to see and experience the venue without physically being present inside the venue.
  4. CSA will provide a dedicated volume of time for each person per week so that everybody gets an equal chance to play. The players who have completed their weekly time slot can still book a slot to play but will be moved to a waiting list. These players will be able to play only if the slot is free and nobody else has turned up to play.

Target Audience

  1. People new to a community
  2. People with busy schedules.
  3. People between the age group 22–55

Design Process

Discovery Phase

The discovery phase is a journey of discovery with the aim of getting to know user pain points, frustration and to gain an understanding of the user. Two methods of research contributed to my discovery.

  1. Qualitative Research
  2. Quantitative Research

I conducted a survey with 4 potential users and interviewed them to collect both the types of data to validate or invalidate the features of the app and discover if I could add other possibilities.

Define Phase

During the define phase, I sorted out the user requirements and the initial ideas to create empathy mapping.

Ideate Phase

During the ideate phase, I used 2 methods to find more elegant, and satisfying solutions to problems that affect a user’s experience of a product.

Scenario:User scenarios describe in detail what users do on an app or a website and why they do it.

I used Information Architecture to structurize and prioritize the information and architecture content that helps users to find useful information and provide the required solution.

Concept

The user lives in a society with 2000 flats. There are four Requirement badminton courts in society. The residents should be able to book a slot to play in the badminton court. The slot time will be of 1 hour. The user can book slots for 3 days in advance at max. Cancellations are allowed. Once booked, the courts are auto-assigned to the user. There should be a penalty when the user doesn’t turn up to play.

Ajay lives in a society with 2000 flats. There are four badminton courts in society. He wants to go for a game of badminton with his wife to the badminton stadium within the community. Being a very busy person Ajay finds it difficult in finding the right time to go and play and whenever he tries to make time and go for a game, the courts are always full and he would have to wait for an hour to get a chance to play. The management observes the issues of the residents and decides to get an app built through which the users can book slots and play whenever they want. Ajay downloads the app and books the slot for a game of badminton. Ajay and his wife play a good 60 mins game and Ajay was very happy with the new app and suggests the app to his friends from other communities.

Information Architecture

Design Phase

During the design phase, I created low fidelity wireframes that help to map out the shell of the interface, its screens, and basic information architecture.

Design Decisions

  1. I maintained consistency throughout the app screens so that the users wouldn’t have to wonder whether different words, situations, or actions mean the same thing.
  2. The design eliminates error-prone conditions and presents users with a confirmation option before they commit to the action.
  3. It takes 6 steps for the user to complete a booking such that the system can cater to both inexperienced and experienced users without having to worry about any complex situations or too many functions happening simultaneously.
  4. I used icons to represent certain actions so that the user can co-relate to the words and icons to understand the functionality of that action.
  5. Kept the design clutter-free by keeping only necessary and relevant elements.

--

--