01
People get stuck in a working product
Review a specific journey, use available evidence and identify the decisions that need testing. A focused audit can help you choose what to change first.
UI/UX DESIGN · ARABIC & ENGLISH
A useful interface helps people finish what they came to do. We review the journey, design the screens and test the important decisions before your development team builds them.
Available as a standalone design engagement. Design already included in our website and app packages stays included.
From a task to a clear interface
- The taskWhat is the person trying to finish?
- The journeyWhich steps and decisions belong together?
- The prototypeCan they find the next action without a hint?
- The handoverWhat should happen in every agreed state?
An illustrative design board
A design illustration. Research findings and screens are created for the agreed project.UI/UX design
Journey mappingClickable prototypesArabic / RTLComponent statesDeveloper handover
A DESIGN ENGAGEMENT OF ITS OWN
You may need evidence about an existing flow, a prototype for a new idea or a more consistent component system. We choose the design work around that decision.
02
A new idea needs a usable shape
Connect the main screens into a prototype that you can review with intended users before commissioning development.
03
Different screens behave differently
Define the reusable components, states and content rules your designers and developers need to maintain a coherent product.
DESIGN THAT CAN BE USED
We agree the journeys, screens, languages and research method before starting. The handover records the decisions a developer would otherwise have to guess.
The journey and its friction
Map the task, starting points, decisions and recovery paths. Separate observed problems from assumptions and record what evidence is still missing.
From a task to a clear interface
- The taskWhat is the person trying to finish?
- The journeyWhich steps and decisions belong together?
- The prototypeCan they find the next action without a hint?
Journey mappingClickable prototypesArabic / RTLComponent statesDeveloper handover
Screens connected into a prototype
Design the agreed flow and its important states. A clickable prototype makes navigation and decisions reviewable before they become production code.
Arabic designed alongside English
Review direction, mixed-language content, numbers and realistic text lengths. Include language switching and forms in the journey instead of treating them as a final translation pass.
A bounded research plan
Agree the participants, tasks, method and consent arrangements. Record findings with their limits and turn them into prioritised design decisions.
Accessibility checks in the design
Review the agreed contrast, focus, labels and interaction states. Document the behaviour developers must implement and test; design review alone does not certify a built product.
Files and decisions for the build
Hand over organised design files, reusable components and state notes within scope. Agree review points with developers and record remaining questions before sign-off.
HOW THE DESIGN TAKES SHAPE
Design progresses through evidence, prototypes and feedback. We agree who can approve a direction and how a new request changes the scope.
Define the task and the decision
Review the product, user groups and available evidence. Agree the journey to study and what the team needs to decide at the end.
A brief you can test
- User groups and key tasks
- Available research and analytics
- Scope, reviewers and decision owner
Connect the steps
Map the flow and create wireframes. Include failed, empty and interrupted states while the structure is easy to change.
A journey with its exceptions
- Information and navigation
- Forms and error recovery
- Arabic and English structure
Try the prototype
Review the prototype and run the agreed research. Observe what people do, record where they struggle and distinguish findings from suggestions.
Evidence for the next revision
- Neutral task instructions
- Findings and their limits
- Prioritised design changes
Make the design buildable
Prepare the files and interaction notes. Walk through the agreed states with the development team and record any decisions still open.
A practical handover
- Components and state coverage
- Content and accessibility notes
- File access and build questions
CONCEPT WORK
These demo concepts illustrate possible interface directions. They are not client projects, user-study findings or evidence of a measured conversion improvement.
A journey towards a booking
A booking concept makes the sequence of choices visible. In a real engagement we would test the task, labels and recovery states with the agreed audience.
A workspace with recurring patterns
A product workspace provides a starting point for discussing navigation and reusable components. Its behaviour and accessibility need their own design and implementation checks.
DESIGN ENGAGEMENTS
Each engagement is quoted against a defined journey, screen set or component scope. A review can stand alone or inform a later design and build.
UX audit
Review a journey
For an existing product with a question about usability or a recurring point of friction.
Proposal after scope review
- Review of the agreed journey and evidence
- Findings with severity and supporting observations
- Prioritised recommendations and open questions
- A review session and decision record
Product design
Design and test a flow
For a new or changing product journey that needs a reviewable prototype.
Proposal after scope review
- Agreed journeys, screens and interaction states
- Arabic and English design coverage as scoped
- Clickable prototype and agreed validation method
- Organised files and developer handover notes
Design system
Build the design foundations
For a product team that needs reusable components and clearer design ownership.
Proposal after scope review
- Audit of the agreed interface patterns
- Component and token definitions within scope
- State, content and accessibility guidance
- Handover and an agreed maintenance model
The proposal sets the screen and state coverage, languages, review rounds and file handover. Participant recruitment, incentives, specialist research tools and development are separate unless included. Website and app packages retain their included design; overlapping work is identified before a new scope is agreed.
BEFORE THE DESIGN BRIEF
Yes. This is a standalone design service. We can hand over the agreed files, prototype and notes to your development team. Building, deploying and maintaining the product are separate unless the proposal includes them.
Yes, those packages retain their published design work, prototypes and handover where listed. A separate UI/UX engagement is useful when you need design on its own, a review of an existing product or research beyond that build scope. We identify overlap before agreeing additional work.
We agree the language and content scope at the start. The design considers right-to-left layout, mixed-direction text, realistic labels, numbers and form states alongside English. Translation responsibilities and content approval are recorded in the proposal.
User testing can be included with an agreed research plan. We define the participant criteria, tasks, recruitment responsibility, recording permissions and method before sessions. Small qualitative studies can uncover problems in the tested journey; they do not establish population-wide percentages or prove that every user group is covered.
We can include specified accessibility checks and implementation notes in the scope. A design file cannot prove the accessibility of the finished website or app: keyboard behaviour, assistive technology support and other implementation details must also be tested. We agree the standard, coverage and responsibilities rather than promise a certificate from a design review.
The proposal names the deliverables, including design files, components, prototype and state notes where included. We agree file access, assets, third-party licences and the handover format. Developers should be able to see the approved behaviour and the questions that still need an answer.
We price the work after reviewing the journeys, screens, states, languages and research needs. A focused audit and a full product design system are different engagements. The proposal confirms deliverables, review rounds, timing and price before work begins.