UXDI Rapid Prototyping: Keep Up, Keep Fit

I created a prototype for a fitness app that aims to keep its users informed of upcoming fitness events and simplify the registration process of these events.

For this project, we were given a list of topics to choose from and create an app for. The topic I chose was fitness.

First, we were asked to predict a few pain points that might surface in our user interviews.

Next, we came up with a list of unbiased questions to conduct user interviews with our classmates.


I begin my user research by interviewing a few of my classmates.

Interview with Sneha
Interview with Zoe
Interview with Glen

As fitness is a big part of my brother’s life, I decided to interview him to gather more data.

Interview with my brother, Benjamin


I consolidated the data from the four users I interviewed.

Glen (blue), Zoe (pink), Sneha (orange), Benjamin (green)

Using an affinity diagram, I grouped my findings into different categories — Time, Motivation, Community, Cost, Being Informed. In addition to these, I uncovered one very specific problem which could not be put into these categories — the tedious process of keying in personal details while signing up for fitness events.

Affinity diagram according to categories

While time, motivation, and community appeared to be common problems among the users I interviewed, I was not confident of solving these problems within the timeframe that I had.

After brainstorming for possible solutions to these problems, I decided to focus on and solve the following problem statements:

  1. “It’s difficult to keep track of all the fitness events happening all the time.”
  2. “It’s frustrating to key in my personal details every single time I register for an event.”

These are the respective solution statements:

  1. Create a mobile platform for fitness fanatics to keep them informed of all upcoming fitness events and programmes.
  2. Create a service for users to enter their personal details just once, and register for events as they come up.


In order to recall the usual steps taken to register for an event and create an accurate user flow, I attempted to register for a fitness event online as far as I could go without having to make payment.

First user flow draft

I created two user flows — one for first-time users and one for returning users. This helped to clearly indicate the three less steps that returning users would have to go through, proving the increased convenience and ease that comes with this service.

Storyboard developed based on problem statements

Creating a storyboard helps others better understand the problem. A better understanding of the problem will lead to better and more effective solutions.


Paper prototype

This is the series of screens that a returning user would be presented with throughout the process of registering for an event.

This is what I imagine the app would look like in its more advanced stages of development:

Home screen of a future prototype

The home page would be a scrollable screen with upcoming fitness events. Returning users would be able to just tap on any event and register for it without having to key in their personal details. The notifications function would allow users to select which events they would like to receive notifications about, ensuring that they would not miss out on any information regarding events of their interest.


The immediate next step would be to refine and develop my prototype further, and then conduct usability testing on users.

One future development of this app would be to collaborate with local gyms and fitness companies to list their programmes in this app. This would provide them with a platform to promote any current or upcoming programmes that they might have.


Initially, I thought it would be easier if I chose a topic that I was familiar with and had experience in. However, I realised that my familiarity with the topic might have activated my personal bias, especially during the user interviews. My knowledge of the topic occasionally resulted in me asking the users leading questions (instead of how, what, and why), which was not ideal. In hindsight, I should have chosen a topic that I was less familiar with, or made a more conscious effort to be more aware of my bias and keep it in check.

As this was my first time conducting user interviews, I felt rather awkward and uncomfortable with silences. This resulted in me asking leading questions in order to keep the conversation flowing constantly. It would have been better if I gave myself time to craft better follow-up questions during the interviews.

Overall, this project was an eye-opener to the UX world for me and it gave me a clearer picture of part of the job scope of User Experience Designers.

Click here for prototype.

Like what you read? Give Deniese Chia a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.