Build your own Uber.

# Build an original app inspired by Uber

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 ride request prototype called Wayride, inspired by Uber. It is for a controlled pilot or dispatch demonstration with riders and approved test drivers. The main journey is choosing pickup and destination, receiving an estimate, requesting a ride, accepting it as a driver, and progressing through trip states. This is dispatch software, not an authorization to operate a transport service.

## Design
Use an original map-led mobile interface with a rider request sheet and a driver job view. Always show current trip state, pickup/destination, estimate assumptions, cancellation, and connection status. Give drivers a clear accept/decline action and avoid interactions requiring attention during driving.

## Features
1. Roles: authenticate riders and test drivers, maintain driver approval and availability, and prevent clients from assigning their own role or bypassing approval.

2. Places and estimates: use a configured map/geocoding/routing provider for pickup and destination. Quote a simple documented pricing rule from route distance/time and label estimates; use original demo coordinates only in a clearly marked simulation.

3. Dispatch: create a trip request, offer it to an eligible driver, expire offers, and atomically accept only one driver. Handle cancellation and unavailable drivers without leaving stuck requests.

4. Trip progress: support requested, offered, accepted, arriving, in-progress, completed, and canceled states with server-authorized transitions. Send timestamped location updates only with permission.

5. History and pilot operations: show trip history and an operator view for stuck requests. Use no-payment trips in the MVP, stop location collection when the trip ends, and document operational limits.

## Tech stack
Use Flutter/Dart for a new mobile client and Go with PostgreSQL for the dispatch backend. Use WebSocket or equivalent live updates and a real configured mapping service. Keep credentials and dispatch logic server-side, request location permission explicitly, and avoid background tracking unless specifically authorized. Provide a simulation mode when real map or location APIs are unavailable, with obvious labels.

## Data & behavior
User; Driver {id, userId, approved, availability}; Vehicle; Trip {id, riderId, driverId, pickup, destination, estimateSnapshot, status, version}; DispatchOffer {id, tripId, driverId, expiresAt, acceptedAt}; TripLocation {tripId, driverId, coordinates, timestamp}; TripEvent. Use atomic acceptance and validated state transitions. Define retention for precise location data.

Acceptance checks and scope:
Test two drivers accepting the same offer, expired offers, rider cancellation, denied location permission, stale location updates, reconnect, and trip completion cleanup. Verify role authorization directly at the API. Exclude real fares, payouts, background tracking, surge pricing, public transport operations, and unconfigured emergency features.

## 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.