Mawed v2 · مواعد

A two-sided product

Mawed treats Doctor and Patient as two different product journeys joined by the same appointment record. The Doctor controls schedule and availability; the Patient needs a direct path to one clinic, a clear set of slots and a status that reflects the Doctor's decision.

Designing the two sides together matters because each action changes what the other person can see or do next. The value lies in the lifecycle between them, not in two disconnected screen sets.

Discovery by private clinic code

Instead of a public directory, a Doctor deliberately shares a private clinic code, which is also available as a QR code. The Patient uses it to find the intended clinic and continue to available days and slots. This keeps discovery focused on the Doctor–Patient relationship.

One appointment, two people

The Doctor defines working days, hours and appointment duration, then shares the clinic code. The Patient selects an available slot and submits a booking request. The Doctor accepts or declines it; the Patient follows pending, accepted or declined booking states.

A pending-Doctor gate prevents access to the active Doctor workflow until approval.

One Flutter codebase, two roles

Mawed is built with Flutter and Dart. One codebase carries both the Doctor and Patient journeys, so each role gets its own mobile interaction without splitting the product into unrelated implementations.