Technology Division

Design That Removes the Friction

Research, structure and interface design for products people use daily — designed in Arabic first and tested before a line of code is written.

  • Arabic-first interfaces
  • Tested with real users
  • Design system you keep
  • AR+ENDesigned in both languages
  • WCAGAccessibility standard
  • 1Source of truth in Figma

Most usability problems are decided before design starts

They come from unclear structure: too many options, steps in the wrong order, decisions asked for too early. We fix the structure first, then the interface — which is also why our designs survive contact with development.

  • Arabic layouts designed first, not mirrored afterwards
  • Prototypes tested with real users before build
  • A design system your developers can implement exactly
  • Accessibility checked against WCAG, not assumed
What's included

From research to developer handoff

Everything needed to build the product correctly the first time.

  • Discovery & research

    Interviews, competitor review and analytics, turned into decisions rather than a slide deck.

  • Information architecture

    Structure, navigation and flows agreed as wireframes before any visual design begins.

  • Interface design

    Screens designed for both languages, with states, empty cases and errors — not just the happy path.

  • Design system

    Components, tokens and rules so future screens stay consistent without redesigning them.

  • Prototypes & testing

    Clickable prototypes tested with real users on a phone, with findings fed back into the design.

  • Handoff & QA

    Specifications developers can build from, plus a review of the built product against the design.

How we work

From research to a built product

  1. 01

    Research

    We learn who uses the product, what they are trying to finish, and where they give up today.

  2. 02

    Structure

    Flows and wireframes reviewed and agreed before visual design, when changes are still cheap.

  3. 03

    Visual design

    Arabic and English screens designed together, using your brand or a system we build with you.

  4. 04

    Prototype & test

    A clickable prototype put in front of real users; the design changes where they struggle.

  5. 05

    Handoff & QA

    Specs, assets and a design system handed over, then the build reviewed against them.

What we work with

Tools and standards your team can keep using after handover.

Design
  • Figma
  • Design tokens
  • Component libraries
  • Arabic type systems
Research
  • User interviews
  • Usability testing
  • Analytics review
  • Heatmaps
Prototyping
  • Interactive prototypes
  • Motion specs
  • Content design
Handoff
  • Storybook
  • WCAG 2.2
  • Specs for developers
  • Design QA
FAQ

Questions we hear often

  • Yes. Many clients take the design system and specifications to their own team. Everything is handed over in a form another developer can build from.

  • It is not only mirroring. Line height, letterforms, numerals, icon direction and text expansion all change. We design the Arabic screens first, so the English version adapts rather than the reverse.

  • Often. We start with a usability review of what exists, agree the highest-impact fixes, and redesign in stages so you keep shipping.

  • Two structured rounds per phase, which is usually enough because the structure is agreed before visual design. Further rounds are quoted transparently.

Have a product people find confusing?

Send us a link or a prototype. You will get an honest usability review and the three changes that would help most.