Arabic guide for students3 min read
10 UX laws that make or break an experience
A short guide I wrote in Arabic for design students: each law with its rule, why it matters, an everyday example and a product that uses it.
03 // Blog
Blog
Notes on how I think: UX laws, a talk, contests, exercises and process.
Talk · 21 June 20252 min readRequirements vs. expectations in UX/UI design
Notes from a talk I prepared and gave: why products fail in the gap between what was built and what users expected, and how to close it.
Contest · May 2025 · 2nd place2 min readRebuilding a “destroyed” website against the clock
How I approached the ASU UI/UX Contest V5 brief, starting on paper, and what earned second place.
Redesign exercise2 min readRedesigning one of the internet’s most chaotic stores
Arngren is famous among designers for its cluttered homepage. I used it to practise hierarchy, grouping and white space on a real, extreme example.
Visual design exercise2 min readWhat an old newspaper taught me about visual hierarchy
Redesigning a dense front page to control where the eye goes first, next and last, while keeping its classic personality.
UI challenge2 min readDermatology booking in five screens
A short UI challenge: a booking flow for a dermatology clinic with a soft, rounded visual language.
Process2 min readHow I use AI in my design process (and where I don’t)
Lessons from building Rawaa: AI is great for speed and drafts, and bad at deciding what the product should be.
Process2 min readWhy I still start on paper
Pencil sketches from the Banana platform, and why ten minutes on paper saves an hour in Figma.
Product thinking2 min readWhy Rawaa lives inside WhatsApp
The biggest decision in Rawaa wasn’t a screen. It was choosing not to build an app for guests at all.
Research2 min readWhat 56 students taught me about money apps
Survey numbers and honest quotes from the Filis research, and how each one turned into a design decision.
Design systems2 min readOne card, six verticals
How a single listing card fixed more of a classifieds marketplace than any page redesign could.
Checklist2 min readThe accessibility check I run before handoff
Five quick checks that catch most problems before a developer ever sees the file.
Localization2 min readDesigning for Arabic is not flipping English
What localizing the Tesco homepage, and building this site in two languages, taught me about right-to-left design.
UX research2 min readPersonas that actually change the product
In Legacy, four very different buyers shaped four specific features. Here is how I write personas so that happens.
Process2 min read46 grey screens before any colour
Why I wireframed every screen of Rawaa in grayscale first, and what changed once colour arrived (almost nothing).
Interaction design2 min readDesigning a crisis screen people don’t have to relearn
How Emergency Mode in Filis changes what matters without changing where things are.
UX writing2 min readMicrocopy that helps without judging
Real lines from Filis, and the rules behind them: a number, an action, and no shame.
UX research2 min readCompetitor audits that lead somewhere
Three audits from my projects, and the one sentence each audit had to produce.
UX research2 min readHow I write a usability test plan
Tasks, metrics and heuristics from the Sehati plan, and why I’m honest about what I haven’t tested yet.
Wearables2 min readDesigning for a two-second glance
Lessons from a smartwatch flight tracker: one decision per screen, high contrast, and ruthless priorities.
Design systems2 min readVariables, not hex codes
How Filis runs on 201 Figma variables in five collections, and why every name describes a job, not a colour.
Design systems2 min readDark mode with one switch
Banana’s colours live in Day and Night modes, so the whole platform changes theme without redrawing a single screen.
Prototyping2 min readA prototype with no dead ends
Rawaa’s prototype links 62 screens on desktop and mobile. The rule I used: every screen needs a way forward or a way back.
UX research2 min readFlows before screens
In Sehati our team mapped five user flows with every decision point. The waiting list exists because of one decision point.
