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
Notes from my own projects, a talk and contests, plus short practical guides on UX, accessibility and Arabic (RTL) design.
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.
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.
How I approached the ASU UI/UX Contest V5 brief, starting on paper, and what earned second place.
Arngren is famous among designers for its cluttered homepage. I used it to practise hierarchy, grouping and white space on a real, extreme example.
Redesigning a dense front page to control where the eye goes first, next and last, while keeping its classic personality.
A short UI challenge: a booking flow for a dermatology clinic with a soft, rounded visual language.
Lessons from building Rawaa: AI is great for speed and drafts, and bad at deciding what the product should be.
Pencil sketches from the Banana platform, and why ten minutes on paper saves an hour in Figma.
The biggest decision in Rawaa wasn’t a screen. It was choosing not to build an app for guests at all.
Survey numbers and honest quotes from the Filis research, and how each one turned into a design decision.
How a single listing card fixed more of a classifieds marketplace than any page redesign could.
Five quick checks that catch most problems before a developer ever sees the file.
What localizing the Tesco homepage, and building this site in two languages, taught me about right-to-left design.
In Legacy, four very different buyers shaped four specific features. Here is how I write personas so that happens.
Why I wireframed every screen of Rawaa in grayscale first, and what changed once colour arrived (almost nothing).
How Emergency Mode in Filis changes what matters without changing where things are.
Real lines from Filis, and the rules behind them: a number, an action, and a respectful tone.
Three audits from my projects, and the one sentence each audit had to produce.
Tasks, metrics and heuristics from the Sehati plan, and why I’m honest about what I haven’t tested yet.
Lessons from a smartwatch flight tracker: one decision per screen, high contrast, and ruthless priorities.
How Filis runs on 201 Figma variables in five collections, and why every name describes a job, not a colour.
Banana’s colours live in Day and Night modes, so the whole platform changes theme without redrawing a single screen.
Rawaa’s prototype links 62 screens on desktop and mobile. The rule I used: every screen needs a way forward or a way back.
In Sehati our team mapped five user flows with every decision point. The waiting list exists because of one decision point.
Contrast is the difference in brightness between text and its background. Learn the WCAG ratios, the common failures and how to test them.
Keyboard users need to see where they are. Learn how to design visible focus indicators, use :focus-visible and avoid hidden focus.
Many people never use a mouse. Design every interaction so it works with a keyboard, in a logical order, with no traps and clear exits.
Alt text should serve the purpose of an image, not just describe it. Learn when to write it, when to leave it empty and how context decides.
Forms are where users complete tasks. Use real labels, helpful hints, clear errors and sensible grouping so everyone can finish them.
Small buttons are hard to hit. Learn the WCAG 2.2 minimum of 24 by 24 CSS pixels, the larger 44 px guidance and how spacing helps.
Animation can cause discomfort or nausea for some users. Learn to respect prefers-reduced-motion and to give people control over moving content.
Screen reader users navigate by headings and landmarks. Structure pages with one h1, ordered headings and clear regions.
Colour should never be the only way to convey meaning. Learn WCAG 1.4.1 and how to pair colour with text, icons and patterns.
LCP, INP and CLS measure loading, responsiveness and visual stability. See which design choices move these numbers.
Physical properties like margin-left break when a page flips to right-to-left. Logical properties follow the reading direction and save you from duplicate CSS.
Mirror icons that express direction, leave the rest alone. A short guide to arrows, chevrons, progress and the cases where context decides.
Arabic interfaces can show 0-9 or the Eastern Arabic-Indic digits. The right choice depends on audience, so stay consistent and let research decide.
Pick Arabic UI fonts by legibility, weight range, pairing with Latin, diacritics support and file size, not by looks alone.
Arabic sentences often contain Latin names, numbers and URLs. Learn how the bidi algorithm orders them and how to isolate text with HTML and CSS.
Not every field should flip. Learn which inputs stay left to right on an RTL page, which use auto direction, and how to align labels and messages.
Arabic text usually needs more line height than Latin, lighter weights can fade, and size may need adjusting. Practical starting points to test.
Translating words is one step. Localisation also covers layout, plurals, dates, units, imagery and tone. A checklist for Arabic products.
A good error message says what happened and how to fix it, in plain words and without blame. Examples, patterns and accessibility basics.
Good button labels name the action: a verb plus an object. Patterns for specific, consistent, translation-friendly labels.
How to plan and run a user interview: set a goal, recruit the right people, ask open questions about past behaviour and listen more than you talk.
Biased wording quietly ruins survey data. Learn to spot leading, loaded and double-barrelled questions and to design clear, balanced answer options.
Nielsen’s well-known advice is often misread. Five users per round can reveal most problems, as long as you test in small rounds and fix between them.
Card sorting shows how people group and name content. Learn the main types, how to prepare cards and how to read results to shape navigation.
Tree testing checks whether people can find items in a navigation hierarchy shown as plain text, without visual design getting in the way.
Jobs to be done frames needs as the progress a person wants in a situation. Learn to write job statements and use them to prioritise features.
Affinity mapping turns a pile of research notes into themes. Follow the steps, turn themes into How might we statements and avoid common pitfalls.
Analytics show what happens and how often; interviews and tests explain why. Learn to use both together, avoid vanity metrics and respect privacy.
RICE and MoSCoW help teams rank work with a shared method. See how scoring works, with an illustrative example, and where these tools mislead.
A good critique improves the work toward its goals. Learn how to set goals, structure feedback, avoid solutioning and handle feedback well.
A type scale gives every text size a reason. Learn how to pick a base size and a ratio, set line height, and make sizes responsive.
A spacing scale based on 4 or 8 points keeps rhythm consistent and handoff simple. Learn the tokens, proximity, and density options.
Name colours by role, not by hue. Primitive and semantic tokens make states, dark mode and theming cheaper to build and maintain.
A grid brings order to layouts. Learn columns, gutters and margins, content-led breakpoints, comfortable line length and CSS grid basics.
Dark mode is not an inversion. Learn soft surfaces, off-white text, elevation by lightness, adjusted accents and how to honour user settings.
An empty screen is a chance to guide people. Learn the four kinds of empty state, what each should say, and how to avoid dead ends.
Icons save space but can confuse. Learn when to add labels, how to keep a consistent grid, and how to make icon buttons accessible.
Visual hierarchy tells people what to look at first. Learn the five levers, the squint test and why removing beats adding emphasis.
Not every button deserves equal weight. Learn the four button levels, the six states, consistent sizing, and button versus link semantics.
The right format and markup keep pages fast and stable. Learn when to use JPEG, PNG, WebP, AVIF and SVG, plus srcset, dimensions and lazy loading.
Onboarding copy should lead with the value, keep steps short, let people skip, and explain permissions in context. Measure it by the first real task.
Use a confirmation only when the action is risky, prefer undo when possible, and write a specific title, consequence and button labels instead of Yes or No.
Voice stays constant while tone adapts to context. Learn the four tone dimensions, write three voice principles, and keep Arabic and English consistent.
Placeholder text disappears, is often low in contrast and is not a reliable accessible name. Use a persistent visible label with optional hint text.
A good handoff covers every state, responsive behaviour, tokens, assets, motion, accessibility, content rules and edge cases, then a review of the built result.
A design system is tokens, components, patterns and documentation. Start with an audit, begin small, name things clearly, and measure adoption.
A strong case study has a clear structure, separates your work from the team’s, is honest about gaps, never invents metrics, and respects a hiring manager’s time.
Use WOFF2, subset large fonts, preload only the critical one, choose font-display with care, and tune fallback metrics to reduce layout shift.
Build mobile-first, use fluid type and content-led breakpoints, keep touch targets usable, avoid horizontal scrolling, and test on real devices.
Match the loading pattern to the wait: know the three response-time limits, choose skeletons, spinners or progress bars, and announce changes accessibly.
No posts match. Try another word or clear the filters.