Heading image with splash, explore, event, and add to calendar screens


The Challenge

We all need social interaction, but in the digital age, research suggests that many people live largely isolated lives. Belong aims to fulfill this need by making it easy for people of similar interests to attend events together. However, with the current app, data shows that on average only 20% of people who say they’re going to an event end up attending.

High Level Goals

  • Determine which features in the product might be hindering users from attending an event
  • Discover what may encourage users to attend
  • Cost-effectively incentivize users

The Solution

I aimed to see which features needed to be included or withheld in order to increase the conversion of accepted invites to event attendees. Features that I tested included add to calendar, share with friends, seeing who is attending, and receiving emails.


I was the product designer on this project and had weekly checkins for design feedback and critique with Salvador Perez Figueroa (Senior Designer, LVL) and feedback from Taylor Schultz in the wireframe phase.


Adobe Creative Suite


August 9 - 23rd 2021



I had a limited amount of time for this sprint, so I used quick but effective research methods starting with a competitive analysis and then moving to user surveys.


Survey Findings

In the surveys, participants expressed a few main factors that influenced their decisions to attend events:

  • They were more likely to attend if someone they knew was going
  • They would remember to attend if they received reminders
  • They would be more likely to attend if the event was in their calendar

Here are some quotes of participants explaining why they might not attend an event:

“ I was with friends and we went [to a] couple of events together. It was nice to have familiar faces with you, as well as meeting new people independently later.”

“Mood swings are real. Sometimes you agree to something, but later you don't feel like going anymore, especially when there's nobody to hold you accountable.”

“[I] wasn't too excited about the event anymore; couldn't see a reason to attend the event, as in how would it benefit me?”


Attend-an-event User Flow

Based on user findings, I drew a user flow that emphasized features I thought might encourage users to:

  1. Attend the event with friends
  2. Get reminders
  3. Add the event to their calendar
sketch of the initial sign up flow
Attend an event signup flow

Design & Validate


I created low-fidelity wireframes and created a prototype in Figma based on the event signup user flow. At this stage, I added a few features such as:

  • Asking for notifications when the app opened
  • A share with friends screen after the checkout process
Explore, Event Details, and Share With Friends screens.

Wireframe Usability Testing

After testing the wireframes with 5 participants, heres what I found: 

  • Many users in testing sessions didn’t utilize notifications permissions popping up at the beginning of the app, and many expressed that they wanted an easier way to add to calendar.
  • Large portion of participants also expressed that they would prefer to attend an event that their friends were going to, while a few said they would just go alone.

High Fidelity Mockups Usability Testing

Based on overwhelming feedback from participants in the first round of usability testing, I dedicated a page to add to calendar after the checkout process.

I tested the high fidelity mockups with 5 more participants. Much to my surprise, each participant enthusiastically added the event to their calendar. Many claimed that they might even forget about the event without adding it to their calendar because they didn’t want notifications from the app.

High Fidelity Mockup screens, including 'add to calendar' and 'share with friends'.


Users that planned to go to the event with friends shared it before checking out, and those who were okay with going alone utilized the share with friends feature after the checkout process.

A few participant quotes from both rounds of testing:

“I’d rather put it on my calendar - I don’t want other notifications” -Kayla

“Unless it’s a brand that I like, I’ll uncheck the receive emails button” -Taylor

“I’m an independent person, so I would have bought my ticket first and then shared” -Renee

“If I know someone else who’s going, I’m more likely to go” -Danny

Key Takeaways


From user surveys to usability testing, the social connection aspect came up again and again. It became apparent that the biggest cost-effective incentive was for users to attend an event with people they knew.

Final versions of the design include entire pages dedicated to the add to calendar and share with friends features, which testing participants confirmed were useful and would make them more likely to attend.

Next Steps

If I were given more time, I would further research ways to encourage users to allow notifications from the app. This could mean asking to allow notifications at a time where users have more trust in the app - i.e. after they attend an event.

Another idea I have is to gamify the app. For instance, every event that users attend would rank them higher in a pool of event attendees. I don’t know how well this approach would work, but it seems like a viable incentive program that would also be cost-effective.

Back to top