(Case study 03 — Mobile app)
A cleaning app that connects clients with trusted cleaners
A two-sided cleaning-services app connecting clients with professional cleaners for booking, order management and secure payments — with 190+ iOS and Android wireframe screens, a white-and-violet UI, edge cases, a clickable prototype and a style guide.
Open the Figma prototype
Product
Neatify
Role
UX/UI Designer
Timeframe
6 weeks
Platform
iOS & Android
Tools
Figma

(The problem)
Clients struggle to find professional cleaning quickly, while cleaners can’t get enough orders or manage their schedules — booking, communication and payment are slow and sometimes insecure.
(The goal)
An intuitive platform to schedule, manage and pay for cleaning, with a simple and transparent experience for both clients and cleaners.
190+
Wireframe screens
iOS and Android
2
Apps, one system
Client and cleaner
66
Final screens
Rebuilt in full auto layout
8
Edge cases
Errors and empty states
(User research)
Two people, one clean home
Two personas built from client-provided information — a busy engineer who books cleaning to win back his evenings and a nurse whose shifts change every week — plus the cleaners who need steady, well-organised work.
AA
Alex Anderson
Software engineer · 32 · busy schedule
“
I’d rather spend my free time relaxing than cleaning.
NEEDS
Book a cleaning in a few taps
Transparent prices before confirming
Track the order status in real time
IJ
Ioana Johnson
Nurse · 27 · changing shifts
“
I want to keep my home spotless while managing my time and budget wisely.
NEEDS
Reliable, affordable cleaners
Reschedule easily when shifts change
Real-time updates to plan her day
Key insights
1
Both clients and cleaners value simplicity and speed above everything — the booking has to fit in a few steps.
2
Most users are 25–35: clear text, strong contrast and comfortable type sizes.
3
Transparent prices and trustworthy profiles (ratings, jobs done) are what makes people book again.
4
Real-time communication — status updates and in-app chat — removes the uncertainty of waiting for a cleaner.
5
Cleaners need the same care: a clear onboarding, availability they control and an honest earnings view.
Chapter 01
Competitor analysis
Understand the people
01
Competitor analysis
UI and UX of Uber, Bolt, Bolt Food, Cleanster and Cleanster Pro — to find strengths, friction points and the differentiators worth building on.
UI conclusions
1
Most competitors use clean, modern visuals with neutral or brand-specific color palettes.
2
Consistency varies — especially between sub-products (e.g., Bolt Ride vs Bolt Food).
3
Visual hierarchy is generally strong, but some apps display too much information at once.
4
There is limited customization or accessibility support (font size, dark mode preferences, etc.).
UX conclusions
1
Task flows are fast and efficient in most apps, especially for returning users.
2
User onboarding varies — some apps are intuitive from the start, others lack helpful guidance.
3
Live feedback and tracking work well in mobility apps, but are weaker in cleaning service apps.
4
Support and post-service experience is often underdeveloped — issues or follow-ups require too many steps.
5
There is room to improve clarity, trust, and personalization across all categories.
Chapter 02
Information architecture & user flow · Wireframes for iOS · Wireframes for Android
Shape the flow
02
Information architecture & user flow
Defined with the Product Owner and stakeholders: onboarding, service booking, cleaner selection, payment, post-service feedback — plus edge cases like unavailable time slots or payment errors.

03
Wireframes for iOS
Over 190 wireframe screens across both platforms, defining structure, layout and content placement before any visual design.
12 screens
Auto-scrolls · drag to browse
04
Wireframes for Android
The same flows adapted for Android, so both apps share one logic and stay consistent.
12 screens
Auto-scrolls · drag to browse
Chapter 03
UI design — booking · Messaging · Edge cases & empty states
Design the screens
07
UI design — booking
UI design of the core flows, applying the white-and-violet palette and the typography system — starting with booking a cleaning, step by step.
8 screens
Auto-scrolls · drag to browse
08
Messaging
Clients and cleaners talk in the app — real-time updates instead of phone calls and scattered messages.
4 screens
Auto-scrolls · drag to browse
09
Edge cases & empty states
Unavailable time slots, payment errors and empty screens — each with a clear way forward.
8 screens
Auto-scrolls · drag to browse
Chapter 04
Style guide · Component library · Clickable prototype · Handoff
Ship the system
05
Style guide
Inter typography for both platforms, a white-and-violet palette, icons and components built in Figma.
Typography
Color palette

06
Component library
Icons, navigation bars, buttons, cards, calendar and payment components shared by the client and cleaner apps.
12 screens
Auto-scrolls · drag to browse
10
Clickable prototype
An interactive prototype covering the main journeys end to end, used to test the flow and the interactions.
Open the Figma prototype
11
Handoff
Figma assets and deployment guides for the development team.
(Feature highlights)
The screens that carry the app

01
Home
The next cleaning as a card: date, time, address and cleaner
Room, bathroom and specials amounts itemised
Checklist, notes and a Message button right on the card
New booking is always one tap away
02
Booking
Address confirmed at the top before picking a date
A progress bar shows how far along the booking is
Days with an extra cost are marked in the calendar
Start time with an AM/PM switch, then continue

03
Choose a cleaner
Your past cleaner first, with rating and jobs done
Other cleaners below, same card, same information
Address and date stay visible for context
One tap to select, Continue to confirm
04
Messages
Chat with the cleaner, with an online status in the header
Pay or Request cleaning directly from the conversation
Messages grouped by day
Photos and voice messages from the input bar

05
Earnings dashboard
Weekly earnings with a day-by-day chart
Hours worked and cleanings done at a glance
Net fare, bonuses and tips broken down
Browse weeks with the arrows
(What shipped)
Key features
01
Quick scheduling of cleaning sessions
02
Order management for both clients and cleaners
03
Secure in-app payments
04
Cleaner selection and post-service feedback
05
Clear handling of unavailable time slots and payment errors
06
Cross-platform typography for iOS and Android
(Final UI)
Two apps, one system
The client app and the cleaner app share the same palette, type and components — from the first booking to the cleaner’s first workshop.
20 screens
Auto-scrolls · drag to browse
KEY FLOW
Cleaner onboarding
From the first launch to the first job: sign-up, verification, skills, experience, ID check, availability and workshops.
20 screens
Auto-scrolls · drag to browse
(Accessibility & handoff)
Ready for development
Every screen in auto layout — iOS 393 × 852 and Android 412 × 917
One palette and type scale shared by the client and cleaner apps
Touch targets of at least 44 × 44 px
Status, progress and errors never rely on colour alone
Components with states, from buttons to the calendar and keyboards
Numbered screens that follow the user flow
(Reflection)
What I learned
1
A two-sided product needs two onboardings — the cleaner’s (ID, skills, availability, workshops) is a product of its own.
2
Edge cases such as a rejected payment or an empty bookings list define how trustworthy the app feels.
3
Designing Android alongside iOS from the start kept both apps on one logic instead of two.
Daniel Grecu © 2026
Back to top
(Case study 03)













































































