Build your own Uber Eats.

# Build an original app inspired by Uber Eats

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original local food-ordering pilot called Mealroute, inspired by Uber Eats. Customers order from a small set of approved restaurants, staff accept and prepare the order, and a test courier records pickup and delivery. Start with one delivery region, one restaurant per cart, and no live payments.

## Design
Use original mobile-friendly customer, restaurant, and courier workspaces. Make item options, availability, totals, promised times, and current order stage visible. Show a truthful status timeline; add a configured map only when genuine location information is available.

## Features
1. Restaurant menus: manage hours, delivery area, categories, items, bounded option groups, allergens supplied by the restaurant, and sold-out states. Restaurant staff can edit only their own menus.

2. Cart and quote: enforce one restaurant per cart, validate option requirements, calculate minor-unit totals and delivery fees on the server, and recheck hours/availability before an idempotent test checkout.

3. Kitchen workflow: accept or reject incoming orders, set a preparation estimate, and transition accepted orders through preparing and ready-for-pickup. Capture item/price snapshots so menu edits cannot rewrite an order.

4. Courier assignment: offer an order to eligible test couriers, accept exactly one assignment atomically, and allow only that courier to record pickup and handoff. Keep delivery addresses out of unrelated courier APIs.

5. Tracking and exceptions: show real order events, support permitted cancellation/rejection and reassignment, and record a reason when an order cannot be fulfilled. Optional location updates must require permission and stop after completion.

## Tech stack
Use TypeScript responsive role-based clients, a Go API, PostgreSQL, and real-time order updates. Use row-level transactions for order/assignment transitions and an explicit background expiry policy for stale offers. Map providers and notifications must be configured honestly; the core pilot can operate on address text and state events.

## Data & behavior
Restaurant; StaffRole; OpeningHours; MenuItem; OptionGroup; Option; Cart; Quote; Order {state, addressSnapshot, totalMinor}; OrderItemSnapshot; Courier; AssignmentOffer; Assignment; OrderEvent. Define allowed actor/state transitions on the server.

Acceptance checks and scope:
Test a restaurant closing before checkout, sold-out items, invalid options, duplicate orders, two couriers accepting one job, cancellation after acceptance, and access to delivery addresses after completion. Exclude public delivery operations, live payouts, route optimization, real payment collection, and scraped restaurant menus.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.