BiteBack — Giving Local Eats a Fair Fight
How We Built It
BiteBack is a full‑stack rewards platform that helps local restaurants compete with big‑chain loyalty programs.
We built a React front end with a simple user flow:
- Discover restaurants
- Earn points
- Redeem rewards
- Claim rewards with QR codes
The app uses local storage to keep points and rewards tied to each user account, and Google Cloud APIs to enable live navigation within our map experience.
We also designed an owner‑facing analytics dashboard that clearly shows the financial lift from loyalty programs—highlighting the real impact of our system and creating an opportunity for other local entrepreneurs to host their rewards on our platform.
Challenges We Ran Into
- Scoping & planning: Despite planning ahead, we hit roadblocks where parts of the logic weren’t fully thought through. Friday was spent debugging and regrouping, but with a clear plan Saturday morning, we were able to streamline development step by step.
- Keeping accounts separate: We initially saw point data and profile changes carry across users. This was fixed by scoping stored data per user and cleanly syncing totals to the backend.
- Designing the rewards logic: Creating a rewards system that appealed to both users and restaurant owners required extensive iteration and revision.
- Maintaining visual consistency: The app spans rewards, maps, profiles, and analytics. Keeping animations, card styles, and interactions consistent took careful attention.
- Technical depth: Many parts of the project pushed us outside our comfort zone, but this challenge accelerated our learning across frontend/backend integration, API usage, and navigation design.
Accomplishments We’re Proud Of
- A complete and complex loyalty system with a simple user experience: earn → redeem → view → delete → claim → repeat.
- Striking a balance between clean, flat UI inspiration (DoorDash, UberEats, McDonald’s, Taco Bell, Moe’s, Chipotle) and a fun, personal visual style.
- A clear owner analytics view that highlights ROI, peak conversion windows, and actionable next steps.
What We Learned
- How to plan and implement navigation for a multi‑page web application.
- The importance of keeping the entire team aligned on project goals and feature purpose.
- Small UX details—like redemption eligibility, clear feedback, and consistent visual behavior—make loyalty systems feel trustworthy.
- Per‑user data isolation is critical in multi‑account systems.
- Showing impact in plain numbers (revenue lift, conversion rate, ROI) is what makes a product valuable to restaurant owners.
What’s Next for BiteBack
We want to turn BiteBack into a real alternative to enterprise loyalty platforms. Planned next steps include:
- Live transaction data
- POS integrations
- Automated marketing campaigns
- A deeper owner dashboard with retention and lifetime value metrics
Our goal is simple: give local restaurants the same loyalty power as big chains—without the big‑chain budget.
Log in or sign up for Devpost to join the conversation.