Work · Mobile Apps

A mobile app you can use — not a picture of one

Our Mobile Apps page describes the service. This concept shows the standard: a fictional home-services booking app with a real, working flow. Use the phone below exactly as a customer would — filter services, book one, pick a time, and find the booking on the Jobs screen.

DEMO / CONCEPT

App concept — not a delivered product. A fictional home-services booking app, designed and wired as a clickable concept. No real business, bookings or payments exist behind it.

HOME SERVICES

What does your home need?

Tap a service to start a booking. Category chips filter the list.

BOOKING

Choose a service first

Pick a time

Simulated: confirming creates a pretend booking on the Jobs screen. Nothing is booked, charged or sent.

Booking received

—

Reference: DM-0000 (simulated)

In a production app this is where the confirmation, technician assignment and reminder schedule would appear.

MY BOOKINGS

Upcoming

No bookings yet. Book a service from the Home screen and it will appear here.

PROFILE

Demo User

Cairo · demo account

Saved address— (concept only)
PaymentCash after service (concept)
LanguageEnglish / العربية

What this concept demonstrates

  • A complete booking flow in four taps: browse, filter, pick a time, confirm.
  • One design system across five screens — type, spacing, colour and components stay consistent.
  • Honest empty states: the Jobs screen says what will appear there before anything exists.
  • A bilingual-ready layout: the same screens run in Arabic with full RTL mirroring.

The flow is wired, not drawn: every control on the phone works. What it does not have — deliberately — is a backend, accounts, or payments; those are scoped per client engagement.

What is real here — and what is simulated

Implemented on this pageThe five screens, navigation, category filtering, service selection, time-slot selection, the confirmation state and the Jobs list update — a complete front-end flow in your browser.
SimulatedThe business, services, prices and booking itself. No backend, account, payment or notification exists behind the concept.
In a client engagementThe same design system and flows are built as a real cross-platform app (Android and iOS from one codebase), tested on real devices, and released to the store from the client's own accounts.

← Back to selected work

Have a project in mind?

Tell us what you are trying to build or fix. We reply with honest next steps — including if we are not the right fit.

Start a project