Case Study
How this project was designed and delivered
Overview
Kravein helps food lovers discover specific dishes and drinks nearby, not just venues. Users browse trending dishes, see photos and reviews from other foodies, follow favourite places, and (where available) order food or book tables directly from the app and website.
Problem
Most restaurant platforms are venue-centric and make it hard to answer a simple question: where is the best burger, laksa, or cocktail near me? Kravein wanted a food-first experience, where reviews and discovery happen at the dish level, and where users can move seamlessly from discovery to ordering or booking.
My Role
I worked as a frontend engineer on the marketing and discovery web experience, collaborating with product and design to refine search and browsing flows. I owned the integration with the GraphQL backend, built reusable UI components for dishes and venues, and focused heavily on performance and mobile UX.
Solution
Using Next.js and Apollo GraphQL, I implemented SEO-friendly pages for dish, venue, and location-based discovery, along with reusable card components for dishes, venues, and reviews. The site surfaces curated sections like trending dishes, lets users explore venue details and menus, and funnels them into the native apps for deeper engagement and ordering.
Outcome
The final experience gives Kravein a fast, image-rich web presence that reflects its food-first brand. It makes the content easily discoverable via search, provides a clear path from browsing to action, and gives the team a flexible frontend architecture that can support new features like events, offers, and bookings on top of the same GraphQL APIs.
This write-up focuses on the product problem, my role, and the key architectural decisions behind the implementation, highlighting how design, engineering and UX came together.
It is intentionally high level and technology-agnostic so it can be read easily by both engineers and non-technical stakeholders.