Product design for healthcare is different from product design for consumer apps in one fundamental way: the stakes of confusion are higher. An unclear navigation pattern in a social app is an annoyance. An unclear medication schedule in a health app can lead to a missed dose. Our design philosophy is built around that difference.
Principle 1: Clarity over cleverness
We do not use design as a vehicle for demonstrating creativity. Every visual element on the platform has a purpose: to communicate information, to indicate an action or to provide feedback on a completed action. If removing an element doesn't change the user's ability to do what they came to do, we remove it.
Principle 2: Bilingual by default
Designing for Arabic and English simultaneously is a genuine design constraint, not an afterthought. The two languages have different reading directions, different text densities for equivalent content, and different conventions for dates, numbers and formatting. We test every design in both languages before it ships.
Principle 3: Honest about uncertainty
When the AI analysis is uncertain, we say so. When a lab result is at the boundary of the reference range rather than clearly inside or outside it, we describe it as a boundary value, not as normal or abnormal. Honest design in healthcare means acknowledging complexity rather than flattening it into false certainty.
What we got wrong early
Our first version of the record upload flow required users to categorise every document before uploading it. The categorisation taxonomy was logical from a data architecture perspective and frustrating from a user perspective. We replaced it with automatic categorisation based on document content — and the upload completion rate went from 61% to 89% immediately.