Owned product · 2025 – Present

Quick Food

A live food-ordering storefront with a searchable Sanity-backed menu, persistent cart, authentication, saved addresses, Stripe Checkout, Sanity order creation, and order tracking.

View live demo

Quick Food homepage with menu picks and cart prompt

01 Scope

The product context behind the work.

Problem

A food-ordering product has to keep discovery, cart, identity, delivery, payment, and order state coherent while protecting checkout and the hosted demo against invalid requests, deployment failures, and inconsistent responsive states.

My contribution

The product connects a Sanity-backed menu, search and filtering, persistent Zustand cart, NextAuth account flow, saved addresses, Stripe Checkout, Sanity order creation, and order tracking
Umar implemented request rate limiting and checkout hardening around authentication, cart validation, saved-address state, payment handoff, and invalid or repeated submissions
Umar delivered deployment fixes for environment-sensitive build and hosted-demo failures
Umar led UI QA across responsive menu, product, cart, checkout, address, and order states and closed the resulting delivery issues

02 Approach

Important engineering decisions.

Quick Food is a live food-ordering product. Customers can search and filter a Sanity-backed menu, inspect an item, keep selections in a persistent Zustand cart, authenticate through NextAuth, choose a saved address, complete Stripe Checkout, and follow the resulting order.

The connected customer journey spans Sanity menu content and order creation, search and filters, account access, saved addresses, cart continuity, payment handoff, and order tracking.

Umar's direct engineering contribution focused on reliability. He added request rate limiting, hardened checkout around authenticated state, cart and address validation, payment handoff, and invalid or repeated submissions, and resolved environment-sensitive deployment failures affecting the hosted demo.

Umar also led responsive UI QA across menu, product, cart, checkout, address, and order states, then closed the resulting delivery issues. The public case keeps his contribution specific: rate limiting, checkout hardening, deployment fixes, and responsive UI QA.

03 Evidence

Product screens from the shipped flow.

Quick Food menu browsing screen — The menu browsing screen presents food cards with categories, concise descriptions, ratings, prices, quantity controls, and add-to-cart actions.

Quick Food product detail screen — The product detail screen gives the customer product imagery, price, readiness state, meal attributes, option selection, and subtotal feedback.

Quick Food shopping cart and checkout screen — The cart screen keeps selected items, quantity controls, delivery address state, and order summary visible before checkout.

04 Delivered & verified

What the public proof supports.

Delivered scope

Customer flow

Search and filters lead into product detail, a persistent cart, saved addresses, Stripe Checkout, and order tracking

Product system

Sanity powers menu content and Sanity order creation, NextAuth handles account identity, and Zustand keeps cart state

Umar's contribution

Rate limiting, checkout hardening, deployment fixes, and responsive UI QA strengthened the live product

Stack

Next.jsReactTypeScriptTailwind CSSSanityNextAuthStripeZustand

Reflections

A food-ordering product is a connected state system: catalog, cart, identity, address, payment, order creation, and tracking all need to agree.
The clearest contribution story stays specific: ship the full journey, then close rate-limit, checkout, deployment, and UI QA gaps.

Next step

Have a similar project?

If this looks close to the product work you need, book a short call and I will help scope the next step clearly.

Book an intro call