Digital Products

UI and UX Design

User research, tested prototypes and Arabic and English screens that developers can build without guessing.

Add to project estimate

Users judge a website or system by whether they can finish their task. When a form asks for the same information twice, buttons are hard to find, or the Arabic screens are an afterthought with broken alignment, people call your staff, make mistakes or give up. Fixing these problems after development is slow, because the screens are already built and connected to everything behind them.

Kemlat designs the user experience (UX), meaning how a product works for the person using it, and the user interface (UI), meaning the screens, layouts and controls. We start with research into who the users are and what they need to do, map their user journeys, and test clickable prototypes before development. The final screens come with a design system so developers build the Arabic and English versions consistently.

How we work

  1. 01

    Research users and tasks

    We interview or observe a sample of users, review support requests and any usage data, and list the main tasks of each user group. This shows where people struggle today.

  2. 02

    Map user journeys

    For each main task we map the steps users take, the decisions they make and the points where they stop or call for help. These user journeys show which screens are needed and in what order.

  3. 03

    Prototype and test

    We create clickable prototypes of the key flows and test them with real users, noting where they hesitate or make mistakes. Changes at this stage are far easier than after development.

  4. 04

    Design the final screens

    We design the final screens in Arabic and English, right to left and left to right, with readable text sizes and clear contrast. We also design how each screen looks while loading, when empty and when showing an error.

  5. 05

    Build the design system and hand over

    We collect colours, fonts, buttons, form fields and other parts into a design system, a shared library that developers reuse. We then review the first built screens to confirm they match the design.

  6. 06

    Review after launch

    Where analytics or support data is available, we review it with you to choose the next screens worth improving.

What you receive

User research summary

Findings from interviews, observation and data, with the main tasks and difficulties of each user group.

User journey maps

Step-by-step maps of the key tasks, showing where the current or planned experience breaks down.

Interactive prototypes

Clickable prototypes of the key flows, tested with users and revised based on what was observed.

Final interface designs

Approved Arabic and English screens for all agreed pages, including loading, empty and error views, ready for development.

Design system sized to the product

From a simple style guide for a website to a full library of reusable screen parts for a platform, with files and notes for developers.

What changes for you

  • Users complete key tasks with fewer errors and fewer calls to your staff.
  • Developers build from approved designs instead of guessing.
  • Arabic and English versions look and behave the same way.
  • Design decisions rest on what users did in testing, not on personal preference.

Scope: This service covers design, not development; the screens can be built by Kemlat or by your own developers. The number of screens and user test sessions is set in the agreed scope.

Questions clients ask

Do we need user research if we already know our customers?

Your team knows the customers, but usually not exactly how they use the screens. A few interviews and prototype tests reveal problems that internal reviews miss. We size the research to the project.

Which design tool do you use, and do we receive the files?

We usually work in Figma, a widely used design tool that developers can open in a browser. All files are shared with your team during the work and handed over at the end.

Can you redesign only part of an existing system?

Yes. We can focus on the flows that cause the most trouble, such as registration or checkout, and design them to fit the rest of the system.

How do you handle Arabic design?

Arabic screens are designed from the start, not mirrored at the end. We check text direction, icons that must flip, number formats, and fonts that stay clear at small sizes.

Start with a conversation

Tell us where you are today. We will suggest the right first step, with no obligation.