Skip the canvas and read this as a normal page

Open to mid-level and senior roles · Available now

Hey you, I’m Abdullah.

Designer by trade. Researcher by habit.

A product designer who owns problems end to end: framing them with research, shaping the answer with product and engineering, and checking after launch whether it actually worked.

Abdullah Omer in his design studio, leaning on his desk
1M+
downloads on Qur’an for All, which I redesigned end to end
0% → 92%
save-for-later task completion after the redesign
2.1 → 4.5
player ease out of 5, against targets set before testing
1,000+
legal professionals using Malakah, the AI workspace I designed

Pakistan. Remote or on-site, worldwide. Open to relocating to London, UK.

I design trust-first experiences for sensitive data.

Product designer with 4+ years across EdTech, LegalTech, FinTech, AI and enterprise, working with PMs, engineers and researchers from research to handoff.

What I specialise in.

Permission and sharing models, source attribution for AI answers, and the internal tools behind them. I’ve shipped a consumer mobile app used by 200K people a day and bilingual Arabic and English products for Saudi Arabia.

An audit nobody asked for.

A friend mentioned that the Qur’an for All app felt outdated. I audited it on my own for my portfolio and sent it cold to the institute’s founder. They hired me to lead the redesign.

  • Interaction Design
  • User Research
  • Usability Testing
  • Information Architecture
  • Design Systems
  • Permissions & Sharing UX
  • AI Trust & Source Attribution
  • Bilingual & RTL Design
  • Consumer Mobile
  • Internal & Admin Tools
  • Figma
  • Miro

Jan 2026 – Present

Full-time

Product Designer (Lead)

Al-Huda Welfare Foundation

Led the end-to-end redesign of Qur’an for All, a consumer iOS and Android app with 200K daily users in 90+ countries.

  • Took it from audit and research (~1,900 survey responses, 6 usability sessions) to IA, UI, design system and handoff.
  • Shipped a four-tab navigation, a dashboard-style Home, a new player and visible saved and downloaded state on every row, while keeping the Library structure users had memorised (19 → 12 categories).
  • Re-tested the shipped build on the same tasks: save-for-later 0% → 92%, “is this saved?” first click 0% → 88%, seek errors 4.0 → 0.3, player ease 2.1 → 4.5/5.
  • Led a rotating team of three juniors.
See the work →

May 2024 – Mar 2026

Full-time · Malakah AI legal workspace

Product Designer

Stixor

Designed a bilingual AI contract workspace for Saudi legal teams, used by 1,000+ legal professionals.

  • Led research (12 interviews, 6 mapped workflows, 10 usability sessions), IA, UI and an RTL/LTR design system.
  • Designed a four-level access model with a new Query role, so approvers can ask the AI about a contract without edit rights.
  • Made every claim in an AI answer link to the exact article of Saudi law, opened beside the answer with its version history.
  • Built a legislation CMS and an evaluation tool where the AI team scores retrieval. Redesigned the Malakah.ai website.
See the work →

Mar 2023 – Apr 2024

Full-time

UI/UX Designer

Veroke

Led UX for a generative AI chatbot, and supported enterprise website and app design.

  • Led UX for Talent AI, a GenAI WhatsApp chatbot for job seekers, from research (40+ surveys, 8+ interviews) to an MVP in 4 months with ML and PM partners.
  • Supported website and app design for enterprise projects, including American Express (Saudi Arabia).
See the work →

Jan 2022 – Mar 2023

Onsite

Product Designer

Avialdo Solutions

Improved onboarding and key flows for a platform U.S. unions use every day.

  • Improved onboarding and key flows for LinkedUnion, a mobile and web platform U.S. unions use for dues and member services.
  • Audited the internal tool for setting up new clients.
See the work →

In my words

Click a card to shuffle. Drag to rearrange.

Design for the edges

Start with the people who struggle most; their success is everyone’s.

Question the pattern

“Always done” isn’t always right. Defaults get challenged.

Share the stumbles

Mistakes are data. Talking about what failed makes the team faster.

Skin in the game

Shipped work speaks for you, so design it responsibly.

My process, from research to launch.

Six steps I follow on every project, each one shown in the case studies.

  1. 01

    Audit & research

    Start with what’s broken and who it’s broken for: UX audits, surveys, interviews and following real tasks end to end.

    Qur’an for All: ~1,900 survey responses

  2. 02

    Frame the problem

    Turn findings into a clear problem, the workflows it touches, and the numbers that will say whether we fixed it.

    Malakah: 12 interviews, 6 mapped workflows

  3. 03

    Structure

    Set the information architecture and core flows before any pixels, so the product has a shape engineers can build on.

    Malakah: one access model across 4 levels

  4. 04

    Design & prototype

    Design the UI and the system behind it, including right-to-left Arabic and left-to-right English, and prototype the risky parts.

    Bilingual RTL / LTR design system

  5. 05

    Test & iterate

    Put prototypes in front of real users, watch where they struggle, and change the design before it reaches code.

    Malakah: 10 usability sessions

  6. 06

    Ship & measure

    Work through trade-offs with PMs and engineers until it ships, then measure whether it actually worked.

    Save-for-later completion 0% → 92%

Available immediately

Let’s work together.

Open to mid-level and senior Product Designer roles, remote or on-site, worldwide.

Abdullah Omer · Product Designer · 4+ years

UX audit · Mobile · EdTech · Shipped

Qur’an for All

A daily habit for 200,000 people, rebuilt around find and return.

Explore →

Presentation (PDF) ↗Full case study ↗

Qur’an for All · Overview

A free Islamic learning app with over 20,000 audio lectures and around 200K daily listeners in 90+ countries. I started with an audit nobody asked for, got hired to lead the redesign, and over eight months we shipped a new navigation, home screen and player.

My role
Lead designer: audit, survey, usability sessions, IA, UI, design system and handoff.
Stack & methods
Bilingual survey · Moderated usability sessions · Information architecture · Design system · Figma
Team
Me and three juniors, rotating across phases.
Duration
8 months
  • 200Kdaily users
  • 1M+downloads
  • 90+countries

Qur’an for All · Problem

20,000 lectures behind look-alike tiles.

Every daily feature was hidden in a three-dot menu, and the player, the screen people used most, was the lowest rated in the audit at 2.1/5.

The challenge was to fix this without breaking the habits 200,000 people had already built.

Twenty identical tiles
Features behind a kebab
Seven controls in one bar

Qur’an for All · Research

What people said, and what they actually did.

A bilingual survey ran through the WhatsApp groups and channels where users already were, plus moderated sessions on their own devices, with every task measured against targets agreed in advance.

The survey is self-report and six sessions are directional, so every session finding is either backed up at scale or flagged as unproven.

  • ~1,900

    survey responses

  • 6

    moderated sessions

  • 3 weeks

    collection window

Qur’an for All · Findings

Users didn’t need new features. They needed the existing ones to work better.

Three intents kept surfacing across the survey and the sessions.

  • Find.

    They know what they want. 55% never used Search, because it was hidden.

  • Return.

    They’re mid-series. 60% had saved something they later couldn’t find.

  • Explore.

    No particular goal. The smallest group, and stakeholders chose to prioritise current users.

Qur’an for All · Solution · Navigation

First, the app needed navigation.

A four-tab bar replaced the kebab, each tab mapped to one behaviour: Home is your activity, Browse is discovery, Library is structured content, Search is direct retrieval.

Home became a dashboard: Recently Played, Favorite Audios, Favorite Series and Downloaded.

Before
After

Qur’an for All · Solution · Hardest call

Deciding not to redesign the Library.

Around 200,000 people had already memorised it, so it kept its shape. We only removed the categories the survey showed nobody used, going from 19 to 12.

One taxonomy rule then applied across 20,000+ files: one row per series, variants one level deeper, bilingual titles.

Same shape, 12 cards
One title per row

Qur’an for All · Solution · Player

Playback, rebuilt as two surfaces.

A persistent mini player for the background, and a full-screen player with a real scrub bar and exposed speed control for everything else.

Visible state went on every row: saved, downloaded, or already played.

Mini player
Full-screen player

Qur’an for All · Results

Shipped, then re-tested on the same tasks.

Eight weeks after release, using the same protocol, against targets set before testing. These come from moderated sessions rather than usage tracking, and Browse and onboarding remain unproven.

  • 0% → 92%

    save-for-later completion

  • 0% → 88%

    “is this saved?” first click

  • 4.0 → 0.3

    seek errors

  • 2.1 → 4.5

    player ease, out of 5

Qur’an for All · Learnings

Good judgment sometimes means doing less design.

The next cycle has two goals: analytics in the product, and closing the accessibility gaps that didn’t make the first release.

  • The hardest call was holding back.

    Letting Browse and Library coexist was harder than designing either one.

  • Showing state mattered more than adding actions.

    The tasks that improved most were the ones where the fix was making things visible.

AI trust · LegalTech · Shipped

Malakah Citations

Making a legal AI show its sources, down to the article.

Explore →

Presentation (PDF) ↗Full case study ↗

Malakah Citations · Overview

Lawyers wouldn’t act on an AI answer they couldn’t check. I designed the system that lets every claim in Malakah’s answers open the exact article of Saudi law it came from.

My role
Product Designer at Stixor, for Malakah. Legal chat, legislation CMS and evaluation admin.
Stack & methods
12 interviews · Pattern comparison · Arabic (RTL) + English (LTR) · Internal tools
Team
Lawyers, plus the internal content and AI team as users.
Duration
2024 – 2026
  • 10 of 12would re-check an unsourced answer
  • 1,000+legal professionals

Malakah Citations · Problem

An answer you can’t check is a research task.

A lawyer is accountable for every piece of advice they give. Saudi law also changes, so “the law says” is only useful if you know which version said it.

The reframe: not “make the answer more accurate”, but “make every claim cheap to check”.

The starting point: article numbers, no links

Malakah Citations · Approach

A citation is only as good as the three layers under it.

A source link only works if the law is stored in pieces small enough to point at, and if retrieval reliably finds the right piece.

  • Structure the law.

    A legislation CMS for the content team: chapters, parts, articles, annexes and amendments.

  • Measure retrieval.

    An evaluation tool for the AI team: did the right articles come back, and in what order?

  • Show the source.

    Legal chat for lawyers: each claim links to its article, which opens beside the answer.

Malakah Citations · Solution

Four ways to show a source.

I judged every option by one question: how much work is left for the lawyer between reading a claim and trusting it?

  • A link on every claim won.

    It opens the exact article beside the answer, with the cited text highlighted.

  • Then, the version.

    A correct article in an outdated version is still wrong advice.

Claim-level citations

Malakah Citations · Solution · Content

Making the law addressable.

You can only link to an article if the system knows where each article starts and ends. So the content team rebuilds each law as a tree before it’s published.

  • Source priority.

    Tell “the law says” apart from “a guideline suggests”.

  • A translation check next to Publish.

    An unchecked translation is the wrong text.

Legislation CMS

Malakah Citations · Solution · Quality

Measuring whether the right article comes back.

A wrong article, shown with confidence, is worse than no citation. Teams upload test sets and compare runs by precision, recall, F1 and nDCG.

The citation a lawyer sees is the output of retrieval, so this was the most direct way to improve what they’d trust.

Evaluation tool

Malakah Citations · Results

The claim-to-source pattern shipped.

The source opens as a third panel next to the chat and the contract, so a lawyer can check a claim while drafting without switching tools. Malakah serves 1,000+ legal professionals.

Chat, contract and source, side by side

Malakah Citations · Learnings

Trust is a path, not a badge.

Next, I’d test citation density on long answers, measured by time to verify.

  • The visible pattern depends on invisible structure.

    The CMS and the evaluation tool are what made the citation link true.

  • Design for the people behind the AI too.

    The content and AI teams were users of this system as much as the lawyers.

Permissions · LegalTech · Shipped

Malakah Permissions

Who can see, ask and change a confidential contract.

Explore →

Presentation (PDF) ↗Full case study ↗

Malakah Permissions · Overview

An AI workspace adds a new kind of access: asking questions about a document. I designed Malakah’s permission system, from organisation roles down to a single contract, so legal teams can share without losing control.

My role
Product Designer at Stixor, for Malakah. Access model, role picker, sharing flows and audit trail.
Stack & methods
12 interviews · 6 contracts followed end to end · Arabic (RTL) + English (LTR)
Team
Legal teams, business approvers and org admins as users.
Duration
2024 – 2026
  • 4access levels, one model
  • 1,000+legal professionals

Malakah Permissions · Problem

Every share was a copy nobody could take back.

Drafts went back and forth by email, finance approved in WhatsApp, and 9 of 12 people had sent an outdated version at least once.

Moving contracts into one workspace only helps if sharing inside it is as easy as forwarding an email, and much safer.

Malakah Permissions · Solution · Model

Four levels, each answering one question.

Rather than one long list of permissions, each level answers a single question, in the place where people ask it.

  • Organisation.

    Who is on our team? Admin or Member.

  • Project.

    Who works on this matter? Edit, Query or View.

  • Contract.

    Who can open this document? Per person, per file.

  • Signing.

    Who signs, in what order, until when? With an audit trail.

Malakah Permissions · Solution · Key decision

A role for asking, not editing.

Reading a 60-page supply agreement isn’t what a finance approver wants. With only Edit and View, they’d get edit rights they shouldn’t have, or no way to ask.

Query lets them run questions across a project’s files without changing anything.

Each role is one sentence

Malakah Permissions · Solution · Sharing

Sharing that stays visible and reversible.

The access list sits inside the share window, so you never grant access without seeing who already has it.

  • One click to change.

    Revoking access happens where it was granted.

  • Pending is its own state.

    Invited people stay greyed out, and can be withdrawn before they get in.

Share a contract

Malakah Permissions · Solution · Interface

The interface reflects your access.

Unavailable actions are removed, not disabled. A viewer never meets a button that fails, so the menu itself tells them what their access is.

Ownership is labelled with an Owner badge, plus separate “My projects” and “Shared with me” views.

Owners and shared projects

Malakah Permissions · Solution · Signing

Every signature leaves a record.

Signing involves people outside the company. Access for outside parties can expire, and the audit trail records every view and signature and exports as a certificate.

Five shared statuses

Malakah Permissions · Results & learnings

AI creates new kinds of access.

One permission model shipped across organisation, project, contract and signing, used by Malakah’s 1,000+ legal professionals.

  • Describe the action, not the role.

    A one-line “what you can do” beat any role name, especially across two languages.

  • Show access where it’s granted.

    It did more for safe sharing than a separate settings page would have.

Brand identity · Rebrand · Delivered · 2025

Stixor Brand Identity

From generic purple to engineered clarity.

Explore →

Stixor Brand Identity · Overview

I rebuilt Stixor’s brand guidelines: a story that matches the business, a warmer and more ownable palette, a stricter type system, and a voice that explains instead of hypes.

My role
Design and strategy, as Product Designer at Stixor.
Stack & methods
Positioning · Voice · Identity system · Stationery & merch
Duration
2025

Stixor Brand Identity · Problem

A capable studio with a brand that undersold it.

The first brand book stopped describing the business as the company grew.

  • A story out of step.

    It positioned a multi-industry studio as an AI legal platform.

  • A category-default palette.

    Violet and navy on white, shared with countless SaaS brands.

  • A voice without rules.

    Adjectives gave no guidance on writing a headline or an error message.

The previous brand book

Stixor Brand Identity · Solution

Engineered Clarity.

Every decision follows one test: does it make Stixor clearer? The hexagonal mark kept its geometry, so recognition isn’t lost.

  • Three colours with a job each.

    Charcoal 50, Ivory 40, Orange 10. Orange is never a background.

  • Two type families.

    Helvetica Neue for structure, DM Mono for precision.

Same cells, new energy

Stixor Brand Identity · Solution · Voice

We don’t just claim things work. We explain how.

Three pillars, with rewrites for the moments where tone matters most.

  • Precise, not pedantic.

    “Automate your manual data entry with 99% accuracy.”

  • Confident & direct.

    “Connection failed. Please check your network or refresh the page.”

  • Human, but professional.

    “Welcome. Let’s get your workspace set up in three steps.”

Stixor Brand Identity · Results

Less noise. More signal. Same Stixor.

A brand that matches the work: calm, exact and recognisably its own, with rules simple enough for the whole team to use.

The system in use

Layers