A website or an app may offer excellent services, but if the user loses the way or does not understand the next step, they may leave. User experience design cares that the product is easy and understandable. Interface design cares that it is attractive and consistent. At Al-Narjis we combine the two so the sites, apps, and dashboards we design serve your users and your organization's goals together.
We do not separate beauty from the task. A beautiful screen where the visitor does not know where to press does not serve the goal. A clear screen that looks neglected weakens trust. The work combines both from the first sketch, not as a coat of colour added after the structure has frozen.
These are design outputs. Which of them enter your project is set in the scope, so a full user study is not assumed for a task that is the improvement of one screen.
Many products are designed in English and then flipped into Arabic, and problems appear in alignment, icons, the direction of movement, and type. We design with right-to-left in mind from the start, and we choose Arabic type that stays clear on different screens, so the experience feels natural for an Arabic user.
A late flip breaks more than the margin. A «next» arrow points the wrong way, an icon that means progress is read as going back, and Arabic type that was not tried on a small screen becomes a crowded line. We test the Arabic direction on a phone width and a desktop width before we lock the components.
If the product is bilingual, we do not make English the original and Arabic a copy. Each language has a different length and a different order. A component that fits the English sentence may cut the Arabic one, so we design for the longer language where that is needed.
We respect accessibility principles, such as sufficient colour contrast, readable text sizes, and clear interactive elements, so more people can use your product with ease.
This is not an appendix at the end of the file. A button distinguished only by colour, pale grey text on a light background, and a field that does not look tappable are reviewed with the design, not after it. In the handover we state what was considered, so the developer can keep it when they build.
Discovery: we understand the product goals, the users, and the technical constraints. A constraint discovered late sends the design back. We ask it at the start: what the team can build, and what is fixed and must not be touched.
Structure: we build the site map and the basic user journeys. A journey here is the path of one task, such as completing a request or finding a policy, not a map of every possible page.
Sketches and prototypes: we test ideas early, before the investment in development. The prototype answers: did the user understand the step? If they did not understand it on a sketch without colour, colour will not save it.
Visual design: we apply the visual identity and build the design system. If you do not have an identity yet, graphic design can come first, and we return to the screens after it.
Handover to developers: we deliver organized files and clear specifications to make implementation easier. The specification names the normal state, the error state, and the empty state, because the happy screen alone is not enough to build from.
Because we understand the Saudi user and their expectations, and we connect design to technology. A chatbot or an automation step can sit inside the experience in a consistent way. A help button is not stuck in the corner after the design is finished. Its place is studied with the journey: when a person is needed, and when a page is enough.
We also make the scope of implementation clear. We deliver files ready for developers, and building the software can be discussed according to the project. We do not mix a design promise with a launch promise if the launch is not inside the agreement.
User experience cares about ease of use and the logic of the journey. The user interface cares about visual appearance and interaction. We work on both, and the scope states the weight of each.
Yes. We design for websites, mobile apps, and dashboards. The Arabic direction is tested on more than one screen width.
We make the scope clear with you. We deliver files ready for developers, and implementation can be discussed per project. Design does not automatically mean that launch is inside the agreement.
Yes. We review usability and propose practical improvements, starting from the journey where the user gets stuck, not from redrawing every screen.
Talk to the Al-Narjis bot on the site, or email us.
Operated by Al-Narjs · Freelance document No. FL-272182297 · Riyadh
· AlNarjisai@gmail.com
Privacy ·
Terms ·
Data deletion ·
Refund policy ·
Pricing ·
About ·
Contact