EATS
A restaurant discovery app that gives you relevant recommendations fast. No endless scrolling—just places you'll actually want to try.
Finding food shouldn't feel like homework. Most apps throw hundreds of generic options at you. I wanted something smarter.
This project grew with me. Each rebuild taught me something the previous version couldn't.
›v1: Rails + React (Bootcamp)
Built the core idea during Flatiron. Learned full-stack basics, but the architecture felt limiting.
›v2: Decoupled Frontend/Backend
Experimented with separation of concerns. Better patterns, more complexity than needed.
›v3: Next.js Full-Stack (Current)
Started fresh with everything I'd learned. Cleaner code, faster performance, easier to maintain.
- •Restaurant search via Yelp API
- •User auth with Clerk
- •Saved preferences and favorites
- •Mobile-responsive design
- •Fast server-side rendering
- •Next.js + TypeScript
- •Tailwind CSS
- •Supabase (PostgreSQL)
- •Clerk OAuth
- •Yelp API
- •Vercel
Rewriting can be the right move. Sometimes starting over beats patching indefinitely.
Framework choice matters. Moving to Next.js solved problems I'd been working around for months.
Taste improves with practice. Each version looked better and felt better because I understood the problem more deeply.
