PROJECT / 053 May 2025 — 15 June 2025

HungerBull

A food-ordering experience from the menu to checkout and order tracking.

HungerBull food-ordering interface
HungerBull food-ordering interface

Overview

HungerBull brings together menu browsing, cart management, Stripe checkout, and real-time order tracking. Its backend exposes REST APIs for users, menus, carts, and orders, with role-based access control for the different parts of the platform.

Architecture

System architecture
100%

Scroll to explore the connections, or use Fit to see the full diagram.

A React ordering client with an explicit backend boundaryThe published repository contains the frontend. It integrates Auth0, a configured restaurant API, checkout-session creation, and five-second order polling; backend internals are outside this repository.Customer interfaceDiscover restaurantsBasket + checkoutReact Query hooksRestaurant / order APIsBearer access tokensConfigured APIVITE_API_BASE_URLExternal backend boundaryAuth0Login + access tokenAPI audienceRestaurant interfaceMenu managementIncoming order statusCheckout sessionCreate-session endpointHosted payment handoffUser actionsHTTP requestsAccess tokenCreate sessionManage menuOrder status · polled every 5 seconds

A React ordering client with an explicit backend boundary

  1. Auth0 provides access tokens, which API hooks attach as Bearer authorization on protected requests.
  2. The frontend calls the configured API for restaurants, menu updates, orders, and checkout-session creation.
  3. GET /api/order is polled every five seconds for order progress. Database and payment-provider internals are not present in this frontend repository.

HungerBull · System architecture

Component responsibilities
  1. React and Auth0

    React Query hooks obtain Auth0 access tokens and attach Bearer authorization to protected API requests.

  2. Configured backend boundary

    The frontend calls VITE_API_BASE_URL for restaurants, menus, orders, and checkout sessions. Backend database and payment-provider internals are outside this repository.

  3. Order updates

    The order hook polls GET /api/order every five seconds to refresh order progress.

Why I built this

I wanted to build a product with connected customer and management workflows. Food ordering brought together cart state, role-based access, payment integration, and changing order status in one application.

Use case

A customer can browse food, build a cart, pay through Stripe, and track an order. Role-based access supports the platform's management workflows.

What I learned

  • Connecting menu, cart, payment, and order state across the stack.
  • Applying role-based access control to related API workflows.
  • Integrating an external payment service and presenting changing order status in the interface.

Key features

  1. Menu & cart management

    Browse the food menu and manage a cart before placing an order.

  2. Stripe checkout

    A Stripe-backed checkout connects the cart to the payment workflow.

  3. Roles & order tracking

    Role-based access control and real-time tracking support the order-management experience.

More projects

View all
GitHub
LinkedIn
X