Service marketplace / Web
A clearer route from a service need to a booking.
A marketplace prototype with service discovery, customer and provider dashboards, booking management, and availability controls.
- My role
- Full-stack prototyping
- When
- 2025
- Built with
- Next.js · React · TypeScript · Supabase · Tailwind CSS
Explore how it works
Try it yourself ↓A request becomes a booking.
Choose an available time, submit a sample request, and review it as the provider.
Monday at 11:00 is already held in the sample calendar.
Sample booking
Choose a time and create a request to see its status here.
An in-page illustration of availability and booking states. The original request submission was simulated; this example makes no real reservation.
The challenge
A service marketplace has two perspectives: a customer looking for help and a provider managing availability and bookings. This prototype explores how those workflows can meet in one product.
How I built it
Make room for each role
Marketplace, customer, and provider screens organize discovery and account-specific work. Supabase handles authentication, sessions, and profile reads.
Explore the request journey
A five-step service-request flow guides the interaction. Its submission currently simulates an API response and records success locally, keeping that part of the experience at prototype scope.
Connect the booking workspace
The booking manager reads bookings and updates their status through Supabase. Availability controls and calendar interfaces explore how providers can manage their time.
What came out of it
A marketplace prototype combining implemented account, profile, and booking-data operations with a simulated service-request submission flow.
Sources & project context
- Project README, interface code, and data operations, reviewed October 2026