proud-parking

As a user or parking provider, I want to use the signup page so that I can register an account, verify via email/phone, and set up my profile. Implement based on the existing Signup (v2) JSX design. Connects from Landing page and leads to Profile setup.

As a parking provider, I want to use the slots page so that I can update slot availability in real-time and manage walk-in customers. Implement based on the existing Slots (v2) JSX design. Connects from Dashboard and allows real-time slot status updates.

As an admin, I want to use the disputes page so that I can review and resolve conflicts between users and parking providers. Implement based on the existing Disputes (v2) JSX design. Connects from Providers page and Admin Dashboard.

As a driver, I want to use the home page so that I can browse available parking spots on an interactive map after login and navigate to Search or Parking Detail. Implement based on the existing Home (v2) JSX design. Connects from Login/Signup and links to Search.

As a parking provider or admin, I want to use the dashboard page so that I can view an overview of reservations, activity, and key metrics. Implement based on the existing Dashboard (v2) JSX design. Entry point for provider flow (after Profile setup) and admin flow (after Login). Links to Slots, Analytics, Users, Providers, Disputes, and Reports.

As a driver, I want to use the session page so that I can track my active parking session, view elapsed time and live slot status, and proceed to checkout when done. Implement based on the existing Session (v1) JSX design. Connects from Payment page and links to Checkout page.

As an admin, I want to use the users page so that I can manage user accounts, view activity, and take actions such as suspend or verify users. Implement based on the existing Users (v2) JSX design. Connects from Admin Dashboard.

As a driver, I want to use the payment page so that I can pay the reservation fee using Telebirr, M-Pesa, or card payment and receive a confirmation. Implement based on the existing Payment (v2) JSX design. Connects from Reservation page and links to Session page.

As a driver, I want to use the reservation page so that I can confirm my parking slot selection, review slot details and pricing, and proceed to payment. Implement based on the existing Reservation (v2) JSX design. Connects from Parking Detail and links to Payment page. Include reservation confirmation animation (confetti burst).

As an admin, I want to use the reports page so that I can generate and download analytics reports for parking providers and platform operations. Implement based on the existing Reports (v1) JSX design. Connects from Admin Dashboard.

As a driver, I want to use the checkout page so that I can review my parking session summary and pay the remaining balance after my session ends. Implement based on the existing Checkout (v1) JSX design. Connects from Session page and completes the driver user flow.

As an admin, I want to use the providers page so that I can review, approve, or reject parking provider listings and manage their status on the platform. Implement based on the existing Providers (v1) JSX design. Connects from Admin Dashboard and links to Disputes page.

As a user, I want to use the login page so that I can sign in to my account and be redirected to the Home (driver) or Dashboard (admin/provider) page. Implement based on the existing Login (v2) JSX design. Connects from Landing page and links to Signup.

As a driver, I want to use the search page so that I can filter parking slots by location, price, and availability and select a slot to view details. Implement based on the existing Search (v2) JSX design. Connects from Home page and links to Parking Detail page.

As a user or parking provider, I want to use the profile page so that I can set up and manage my account information, preferences, and listing details. Implement based on the existing Profile (v2) JSX design. Connects from Signup for initial setup and accessible from Dashboard navigation.

As a driver, I want to use the parking detail page so that I can view slot information, pricing, provider rating, and proceed to reserve the slot. Implement based on the existing Parking Detail (v1) JSX design. Connects from Search page and links to Reservation page.

As a parking provider, I want to use the analytics page so that I can view revenue trends, peak hours, and occupancy statistics for my parking lot. Implement based on the existing Analytics (v2) JSX design. Connects from Dashboard and displays provider-level revenue and usage metrics.

As a user, I want to view the landing page so that I can see the interactive city map with live parking updates, animated pins showing availability, and navigate to Login or Signup. Implement based on the existing Landing (v2) JSX design. The page should feature time-based color shifts and micro-interactions as per the signature design concept.

As a user, I want to use the backend API for registration so that I can create an account with email/phone verification and role assignment (driver, provider, admin). FastAPI endpoint for user signup, profile creation, and email/phone verification flow.

As an admin, I want to use the backend API for platform management so that I can monitor activity, manage user and provider accounts, resolve disputes, and generate analytics reports. FastAPI admin endpoints with role-based access control.

As a parking provider, I want to use the backend API for slot management so that I can update slot availability in real-time, manage walk-ins, and handle reservations from my dashboard. FastAPI endpoints for CRUD operations on slots with real-time broadcasting.

As a user, I want to use the backend API for parking search so that I can query available parking spaces by location, price, and availability with live updates. FastAPI endpoints supporting filtering, real-time slot counts, and geolocation-based queries.

As a user, I want to use the AI assistant so that I can get conversational help finding parking, making reservations, and resolving queries. Integrate GPT via Langchain and Litellm for the AI assistant feature available in the dashboard.

As a user and parking provider, I want to use the backend real-time service so that slot availability, reservation status, and session data update instantly without page refresh. Implement WebSocket or SSE-based real-time broadcasting for live parking data.

As a user, I want to use the backend API for reservations so that I can reserve a parking slot, pay the reservation fee, and receive a confirmation. FastAPI endpoints for slot reservation, status management, and confirmation flow.

As a parking provider, I want to use the backend dynamic pricing engine so that parking fees automatically adjust based on demand, time of day, and peak hours to maximize revenue. FastAPI service with pricing rules, scheduling, and real-time fee calculation.

As a user, I want to use the backend API for payments so that I can pay reservation fees and final balances via Telebirr, M-Pesa, or card. FastAPI endpoints integrating local payment gateways with secure transaction handling and receipt generation.

As a user, I want to use the backend API for parking sessions so that I can start, track, and end my parking session with real-time time tracking and remaining balance calculation. FastAPI endpoints for session lifecycle management.

As a frontend developer, I want to connect all implemented pages to their respective backend APIs so that real data flows through the application end-to-end. This includes wiring up search, reservation, payment, session, slot management, and admin pages to FastAPI endpoints with proper error handling and loading states.