Beli Redesign
This personal project stems from my love for this app and my desire to address frustrations with how it tracks user engagement with restaurants. The project focuses on reimagining the process of adding restaurant visit dates and photos, while introducing a greater emphasis on tracking the dishes tried at each restaurant. The key objective is to enhance the user experience and encourage more photo sharing on the app, fostering a richer and more engaging community.
- Encourage more photo sharing
-Add emphasis on experiencing different dishes rather than just restaurants
- Enhance user experience
- Personalize restaurant recommendations through leveraging data on user’s favorite dishes
- In app announcement
- Shorts/ reels announcing restaurants with the best _____
- Restaurant competitions for best _____ dish
- Requires minimal internal team member, majority of the required work includes moving around existing assets and/or adding simple features onto existing pages
- External stakeholders may include restaurants, who will need to confirm their official menus
01. Current Journey
What is the current user journey for the existing features on the Strava app?
After going through the process of adding my own food images from my experience in Carbone, I found that I was unsure of the name of the dish, leading to random labeling of the image. I also found that I was unable to differentiate which photos are from which experience, as I am a regular at this restaurant.
02. Empathize
What are the pain points current users face? Who is the target audience for our solution?
Beli was originally designed to help food lovers consistently find and track the best restaurants. However, in the founder’s "Our Story," they also expressed a vision for the product to "[know] your tastes and [tell] you the places you would love at the click of a button." What better way for the app to understand your tastes than by tracking your favorite specific dishes?
03. Solution
What problem am I solving? What does the design entail?
1. Revise the flow for adding new visits
Rather than entering a date and uploading photos separately, these steps will be combined into a single streamlined process
2. Standardization of dish names:
Instead of freely inputting the dish name, there will be a dropdown menu pre-populated with the restaurants official menu
3. Revamping the “add a new visit date” tab:
New visit details will be displayed differently on the main restaurant page to show user’s dishes from that experience, and enhance clarity
4. Dish count leaderboard:
Adding a leaderboard for “dishes tried” to encourage exploration
Part 1: Revising the Flow
The most significant change is the updated flow for adding images. Instead of going directly to the photo labeling page, users will first be directed to an "Add Visit Date" page. This ensures that photos are properly associated with the date of the dining experience.
Part 2: Standardizing dish names
Part 3: Revamping “add a new visit date” tab
Updating the way visits are displayed provides users with a clearer connection between their dining experiences and the dishes they ordered. Instead of just seeing visit dates, users can now view the specific dishes they tried, along with the photos they uploaded during that visit.
Part 4: Leaderboard for tracking dish counts
Updating the way visits are displayed provides users with a clearer connection between their dining experiences and the dishes they ordered. Instead of just seeing visit dates, users can now view the specific dishes they tried, along with the photos they uploaded during that visit.
Solution Integration
04. Evaluation
What are the details, changes, and improvements with the new feature?
Business Impact
Data analysis opportunities: Opens the door for sponsored dish placements, or providing restaurants with consumer insights
Additional gamification: Leaderboard will encourage users to experience more dishes
More meaningful journal entries: Users get a detailed view of their food journey, making tracking experiences more rewarding
User generated content/ social proof: Users are more likely to take and post images of their food
Measuring Success
Visit-to-log conversion: The % of restaurant visits where users log at least one dish
Photo upload rate: The average amount of images a user posts per restaurant visit
Dish logging frequency: The average amount of dishes logged per visit
Dish logging accuracy: The % of accurately labeled photos to dishes
Evaluation
Thoughts and Reflections
💿 Self Guidance/ Reflection
This was my first time independently conceptualizing and executing a project from start to finish without any initial prompt or guidance. This experience pushed me to think critically about a problem I’m passionate about, refine my perspective through introspection, and develop a solution that feels personally meaningful and impactful.