What am I booking?
Separate service types from optional extras and show a readable summary before requesting a booking.
SERVICE DESIGN · LIVE MARKETPLACE · WEB & ANDROID
From “I need a cleaner”
to a clear next step.
Designing a connected booking experience for customers looking for cleaning services and the professionals delivering the work.
A two-sided marketplace connecting cleaning customers and independent professionals, with clear service selection, booking requests and cleaner work management.
- Role
- Sole product & UX/UI designer
- Platforms
- Web & Android
- Status
- Live product; prototype walkthrough
A booking is a decision about scope and trust.
Customers need to understand what is included in a cleaning service, whether it fits their home and how a request becomes a confirmed appointment. Cleaners need the service details, schedule and request status. Designing the two journeys together makes the work more predictable for both parties.
My responsibility was the end-to-end product and UX/UI design: shaping customer and cleaner journeys, interactions and interface screens.
Reduce uncertainty at each decision.
These are design decisions and hypotheses for usability validation—not claims of measured improvements.
Does it work for both people?
Connect requests to cleaner availability and distinguish requested appointments from confirmed work.
What happens after I submit?
Surface request status and the next action so users know where the booking stands.
Customer journey
Choose a cleaning type → select a provider and time → review details → track confirmation.
Cleaner journey
Set services and availability → review requests → accept work → manage the appointment.
One product, different responsibilities.
Selected published Android screens show how the service supports account access, cleaning options and cleaner workflows. Click a screen to inspect it.
See the published Android app on Google Play.
Try the connected booking journey.
Walk through the customer booking flow and change to the cleaner view to see how the request is handled.
A published product is not proof of impact.
HaeSiivooja is a live website and Android product. This case does not claim conversion improvements or completed user research results. Next, I would test service comprehension, unaided task completion and cleaner confidence when accepting requests.
A polished booking screen matters less than whether both people understand the scope, status and next step.