Return to Home
A Product-Driven Restaurant Discovery Platform for Riyadh
Directory
Food & Beverage
Restaurants
Restaurant discovery in Riyadh is fragmented.
Users rely on Google Maps, social media, and word of mouth, forcing them to jump between platforms just to make a single dining decision.
The result: high effort, low trust, and poor personalization.
There was no platform focused on structured, reliable, and preference-based restaurant discovery.
Overview
Brief App
IOS Platform
·
2024
Role
Senior Product Designer || (UX Strategy · UX · UI)
Freelance
Market
Riyadh, Saudi Arabia
Product Type
Restaurant discovery & directory platform
Food & Beverage Industry
Team
Brief Team
Founder
Tech Lead + 6 Engineers
Operations
Scope • 8 weeks
My Responsibility
Discovery & problem framing · Stakeholder interviews & alignment · User research & competitive analysis · Feature prioritization · Information architecture & user flows · UI design, and handoff.
I worked closely with business and engineering to balance user needs, business goals, and technical feasibility.
Status
LIVE
Designed & handed off for development
Discovery & Research
Early interviews clarified:
v1 must focus on discovery quality, not feature volume
Scope control was critical for launch feasibility
Users
5 real users were recruited based on predefined criteria.
Key insights:
Filtering by context (occasion, mood, suitability) matters more than popularity
Users distrust ads and promoted listings
Real photos and clear data drive confidence
AI is valuable only if accurate and non-intrusive

These shots are from FigJam and mac PDF preview reports.
Competitors Analysis
The Fork · MyTable · Google Maps · WoM · Wddk · Foursquare (City Guide & Swarm)
Gap identified:
Most platforms optimize for maps or bookings, not for decision-making.

These shots are from the Spread Google Sheet for full competitive analysis.
The Turning Point
During feature mapping using an Impact–Effort Matrix, the product scope expanded rapidly—especially around AI features.
I initiated an alignment meeting with:
Founder
Technical Leadership
Decision:
Ship high-impact, low-effort features in v1.
Defer advanced AI features post-launch.
This prevented scope creep and reshaped the MVP.

This shot are from FigJam that display the Impact-Effort Matrix to prioritize the features list.
UX Architecture
Core Flow:
Discover → Evaluate → Decide
The information architecture was designed to:
Support large restaurant datasets.
Enable meaningful filtering.
Reduce cognitive load.
Scale for future features (AI, bookings).

This shot are from FigJam that display the Information Architecture map of the breif app.
UX → UI Execution
UI design focused on:
Readability and consistency
Content-first layouts.
Neutral, trustworthy visuals.
Scale for future features (AI, bookings).
We aim to design the interface to avoid aggressive marketing patterns by design.
These shots are about App Store Preview.
Collaboration & Hand-off
I ran regular check-ins with Business stakeholders & Engineering team.
Delivered:
High-fidelity UI designs.
UX documentation.
Clear developer handoff.
Aligned roadmap for post-launch features.

These shots are from Figma pages and Google Meet that display the handoff & doc meeting.
Outcome & Reflection
This project reinforced that strong discovery significantly reduces rework later in the process, and that effective product design is driven by prioritization rather than feature volume.
If revisited, I would introduce usability testing earlier in the process and define clearer post-launch success metrics to better evaluate impact.
Explore more of my case studies
iWaiter App case study
View the full 0 → 1 process
Mabet Design System 1.0
View the full DS here