Mobile apps · Design concept
A repair-service app concept connecting service choice, a proposed appointment slot and request review, with clear non-confirmation states.
Design concepts, not client projects. Screens are static mockups; names and data are illustrative.
Let a customer describe the service they need and check a preferred appointment before sending a request. The visual flow stops before provider confirmation.
The service screen introduces the repair appointment flow.
The date screen shows 18 September 2026 and the sample 11:00–11:30 selection.
The review brings the intended service and time together without confirming a booking.
A proposed service must explain whether a slot is an appointment, arrival window or preference. Those meanings cannot be inferred from a calendar.
Request review should not use language that promises a technician. A real confirmation depends on the provider’s response.
Proposed design specimens. These are static examples, not working controls or a production specification.
Service canvas
#F4F8FD
Time selection
#286AC1
Request text
#26394F
Clear information. A considered next step.
Use clear sans-serif labels for service names and dates. Give the time range enough space to remain unambiguous.
Separate service choices from calendar controls. Keep the chosen date and time together in the review.
No preferred slot
Choose a preferred date and time before reviewing your request.
Request ready
Your request is ready to review. An appointment has not been confirmed.
Slot unavailable
This slot is no longer available. Choose another preferred time.
A preference entered by a customer does not establish technician availability. The interface should only confirm a booking when the service provider has actually accepted it.
