Algeria AgencyBrand
UI / UX design
Screens your users understand without explanation — tested with real people, not approved in a meeting.
Interface design is not a matter of taste. It is the discipline that decides whether somebody finds the button, understands what is about to happen, and gets to the end. A successful interface is the one nobody mentions, because nothing got in the way.
We work in this order: first what the person is trying to do, then the shortest path, and only at the end the appearance. The reverse order produces screens that please in a meeting and lose users in production.
The decisive test is watching somebody use the screen without helping them. Five people are enough to find most of the problems, and that quarter of an hour of observation is worth more than three approval meetings between people who already know the product.
We deliver designs that can be built: error states, empty screens, loading, text that is too long, and the right-to-left behaviour in Arabic. A design that only shows the ideal case is unfinished — it leaves the hardest decisions to the developer, who will make them without you.
What we usually find
- Your users call you to ask how to do something obvious.
- Your form is abandoned halfway through, and nobody knows at which field.
- Your designs are beautiful, but they show no error cases at all.
- The Arabic version was handled afterwards, and the layout broke.
What changes
Fewer support questions
An interface understood without explanation removes a share of the calls and messages your team handles every day.
Journeys that get finished
Drop-off moves: identifying where people give up and then fixing it produces more than redrawing everything.
Designs that can be built
Error states, empty screens, loading and long text included, so development does not invent the missing decisions.
What you get
Flows before screens
What the person is trying to do, in what order, and what blocks them today.
Complete designs
The normal case, errors, empty, loading, and content longer than expected.
Testing with five users
Watching real people use the screen unaided. Short, inexpensive, and decisive.
Accessibility built in
Contrast, target sizes, keyboard navigation and labels, handled during design rather than corrected after.
Bidirectional from the start
Right-to-left behaviour in Arabic is designed, not adapted afterwards.
A reusable system
Components and rules documented, so the screens that come next stay consistent without us.
How we work
Understand the task
Interviews with the people who actually use the product, not only with those who commission it.
Flow and structure
The shortest path to the objective, sketched and argued before any visual work.
Designs
Complete screens, every state, in both writing directions where that is needed.
User testing
Five people, one task to complete, no help. Problems found are fixed before development.
Handover to development
Source files, rules and components delivered, with the decisions explained rather than left to interpretation.
Is this the right fit for you?
This is for you if
- You have a product whose users complain, or give up without complaining.
- You are about to build and want to avoid paying for the same screens twice.
- Your product has to exist in Arabic as much as in French.
- You accept testing with real people rather than settling it in a meeting.
This is not for you if
- You only want to make what exists prettier, without touching the flows.
- Your problem is that nobody knows the product. That is acquisition, not design.
- You will not build what gets designed. Unbuilt designs are worth nothing.
- You want brand guidelines. That is visual identity, a different service.
What we commit to
Tested with users, not approved in a meeting
We watch five real people use the screen. What they cannot find gets fixed, even if the screen was well liked.
Every state is delivered
Error, empty, loading, long text. A design showing only the ideal case leaves the hard decisions to the developer.
Arabic is designed, not adapted
Writing direction is part of the initial design, because adding it afterwards means revisiting everything.
Designing for Algerian users
Right-to-left is not a mirror. Directional icons change meaning, numbers and prices are still read left to right, and an alignment designed for French ends up on the wrong side. Designing both directions from the start costs little; reconciling them afterwards means revisiting every screen.
The screen sizes actually in circulation are smaller and more varied than the population assumed by standard design files. A screen approved on a large monitor can be unusable on the phone half your users are holding.
Finally, interface familiarity varies widely. Some of your users handle apps all day, others do not. Implicit conventions — swipe to delete, long press for a menu — are not universal, and what is invisible to a designer can be a wall for a user.
Frequently asked questions
Are five people enough to test with?
To find the majority of usability problems, yes. It is not a statistical study: the point is to see where people get stuck, and the same sticking points recur very quickly from one person to the next.
Do you only design, or also build?
Both, together or separately. A design we do not build is delivered with its rules and its states, so your team can build it faithfully.
Can you work on an existing product?
Yes, and it is often the best return on effort: fixing the three screens where users give up costs far less than a full rebuild.
Do you deliver the source files?
Yes, with the components and the rules. You must be able to continue without us, including with a different designer.
Does design really improve sales?
It improves the proportion of people who reach the end of a journey, and that is measurable. It does not replace an offer that fails to convince, and we will tell you if that is where the problem is.
Will you work from our brand guidelines?
Yes, where they exist. We flag the cases where they prevent something important — insufficient contrast, for instance — rather than applying them against the user.
How to start
Send us the screen or the journey that is causing trouble, and tell us what users are trying to do there.
We come back with what we would test first, what we would fix without testing because it is obvious, and an estimate. On an existing product we almost always start by observing before drawing.
What we have written on this subject
An AI writing in Arabic: what breaks in your interface
The Arabic a model produces is correct and your screen no longer is. Here are the eight places it breaks, and the check that finds them in an hour.UI/UX: an interface is judged on a task completed
Not on how it looks. Name the five things people come to do, watch five people do them, and fix what blocks them.Repairing an interface without rebuilding it: where to start
A redesign is the most expensive answer and rarely the right one. How to find the layer the fault is actually in, and fix it there.A small business’s visual identity: what works and what decorates
A logo is not an identity. What is almost always missing is what happens the day after it is delivered.
Let us talk about your project
A free audit, no commitment: we look at your online presence and tell you what is holding it back.
- Tested with users, not approved in a meeting
- Every state is delivered
- Arabic is designed, not adapted