royal-marketplace

As a user, I want to use the frontend Landing page so that I can explore services, navigate to Login or Register, and experience the interactive cityscape design with animated category icons. Implement based on the existing Landing (v2) JSX design. Includes day/night mode cityscape, hero section, and category highlights.

As a user, I want to use the frontend Login page so that I can sign in securely and be redirected to my role-specific dashboard (Customer Home, Provider Dashboard, or Admin Panel). Implement based on the existing Login (v2) JSX design. Includes email/password fields, forgot password link, and role detection.

As a user, I want to use the frontend Register page so that I can create an account as a Customer or Service Provider, complete email verification, and be directed to the appropriate home page. Implement based on the existing Register (v2) JSX design. Includes role selector tabs, full form fields, password strength indicator, Google OAuth button, and terms acceptance.

As a customer, I want to use the backend API for searching and filtering services so that I can query by name, location, rating, price range, and availability and receive paginated provider results.

As a service provider, I want to use the backend API for creating, updating, deleting, and retrieving service listings so that listings include all required fields and go through an admin approval workflow before appearing in search results.

As a customer, I want to use the frontend Home page so that I can search for services by name, browse categories, and be directed to the Results page. Implement based on the existing Home (v2) JSX design. Includes search bar, category grid, featured providers, and quick-access sections.

As a customer, I want to use the frontend Dashboard page so that I can track upcoming and past bookings, cancel bookings, submit reviews, and edit my profile. Implement based on the existing Dashboard (v2) JSX design. Includes WelcomeBanner, StatsCards, BookingsTable, RecentReviews, QuickActions, Sidebar, TopBar, and DashboardFooter sections.

As a service provider, I want to use the frontend Provider Dashboard page so that I can view booking requests, accept or reject bookings, update my availability, manage listings, view earnings, and read customer reviews. Implement based on the existing Provider Dashboard (v2) JSX design.

As an admin, I want to use the frontend Admin Panel page so that I can manage users, approve or reject service listings, monitor all bookings, and moderate reviews (including removing inappropriate ones). Implement based on the existing Admin Panel (v2) JSX design. Includes overview stats, user management table, listing approval queue, booking monitor, and review moderation sections.

As a customer and provider, I want to use the backend API for booking creation, status updates (Pending, Accepted, Rejected, Completed, Cancelled), cancellation, and history retrieval so that the full booking workflow is supported.

As a user, I want the frontend Login, Register, and profile pages to be fully connected to the backend Auth API so that registration, login, logout, email verification, and password reset work end-to-end.

As a customer, I want to use the frontend Results page so that I can filter and browse service providers by location, rating, price range, and availability, and click through to a Provider Profile. Implement based on the existing Results (v2) JSX design. Includes filter sidebar, provider cards, pagination, and sorting controls.

As a customer, I want to use the frontend Review page so that I can leave a star rating and written feedback for a completed service booking. Implement based on the existing Review (v2) JSX design. Includes star selector, text area, and submission confirmation.

As a service provider, I want to use the frontend Listings page so that I can create, edit, and manage my service listings (title, description, pricing, location, availability, category, images) and submit them for admin approval. Implement based on the existing Listings (v2) JSX design.

As a customer and admin, I want to use the backend API for submitting star ratings and written reviews for completed bookings, retrieving reviews per provider, computing average ratings, and allowing admins to remove inappropriate reviews.

As a customer, I want to use the frontend Provider Profile page so that I can view a provider's details (name, image, experience, services, pricing, ratings, reviews) and navigate to the Booking page. Implement based on the existing Provider Profile (v2) JSX design.

As a customer, I want to use the backend API to fetch a provider's public profile including name, image, experience, services, pricing, ratings, and reviews so that I can make an informed booking decision.

As an admin, I want to use the backend API for managing users (view, suspend, delete), approving or rejecting service listings, monitoring all bookings, moderating reviews, and managing service categories so that platform operations remain under control.

As a customer, I want the frontend Home and Results pages to be connected to the backend Search API so that real service listings are fetched, filtered, and paginated dynamically.

As a service provider, I want the frontend Listings page to be connected to the backend Listings API so that I can create, update, and delete my service listings and see their approval status in real time.

As a customer, I want to use the frontend Booking page so that I can select a date and time, review booking details, and submit a booking request to a provider. Implement based on the existing Booking (v1) JSX design. Includes date/time picker, service summary, and confirmation flow.

As a customer and provider, I want the frontend Review page, Provider Profile, and Dashboard pages to be connected to the backend Reviews API so that reviews can be submitted, displayed, and averaged in real time.

As an admin, I want the frontend Admin Panel to be connected to the backend Admin Management API so that I can manage users, approve listings, monitor bookings, and moderate reviews with live data.

As a customer and provider, I want the frontend Booking, Customer Dashboard, and Provider Dashboard pages to be connected to the backend Booking API so that booking creation, status updates, and history are real-time and accurate.

final deployment checks