Back to portfolio
Project dossierSIGNAL-ATLAS.CASE
In Progress2026Featured

SAVR - Context-Aware Dining Platform

A full-stack dining recommendation platform that uses context, preference signals, and explainable flows.

A full-stack dining recommendation platform that uses user preferences, budget, social context, and intent to produce more relevant restaurant and experience suggestions.

SAVR guided onboarding profile setup screenshot

Problem

What this project solves

Restaurant discovery is often generic. It usually filters by location or cuisine, but ignores why someone is going out, who they are with, what mood they want, and what constraints actually matter.

Solution

How I approached it

SAVR treats the dining decision like a context-aware recommendation problem. Users can describe their night, build their night through guided choices, or use a surprise flow to receive explainable recommendations.

Architecture

System structure

01

Frontend application handles onboarding, recommendation inputs, and result presentation.

02

Backend API separates auth, restaurants, experiences, and recommendation routes.

03

Database model supports user preferences, restaurant metadata, atmosphere tags, and future event signals.

04

Recommendation layer maps user context to venue attributes and explains why a result fits.

Decisions

Tradeoffs and outcomes

01

Recommendation input model

Tradeoff: A simple restaurant list would be faster to build, but it would not capture why someone is going out, who they are with, budget, dietary limits, or atmosphere.

Outcome: Structured the product around Describe Your Night, Build Your Night, and Surprise Me so recommendation results can be explained and extended.

02

Backend and frontend contract

Tradeoff: Recommendation features become fragile when UI filters and backend scoring logic evolve separately.

Outcome: Kept API routes, data fields, and result cards aligned around explicit preference signals, restaurant metadata, and explainable output.

03

Proof before polish

Tradeoff: Premium visuals can make a product look finished before the recommendation logic and data model are actually useful.

Outcome: Prioritized working flows, authentication, restaurant data, presets, APIs, and recommendation cards before final visual polish.

Proof

Evidence and impact

01

This is the flagship portfolio project because it combines product thinking, full-stack implementation, recommendation logic, onboarding, and real-world user experience design.

02

FastAPI backend route structure

03

React and TypeScript frontend architecture

04

Authentication and onboarding direction

05

Recommendation flows for Describe, Build, and Surprise modes

Roadmap

Next iteration

01

Expand the proof gallery with recommendation-result screenshots and an architecture diagram.

02

Add a live deployed demo once stable.

03

Add dish-level explanations and event-aware scoring.