Journeys
The three to five tasks that matter most, followed step by step, the way a new user does them.
UX/UI review
Where do peopleget stuck?
For a website, app or dashboard you already have, or one about to launch. We go through it the way your users do, then give you a short list of what to fix first, in order, with examples your developers can work from.
A finding, up close
What we found, and what to do. Every finding shows the screen, what goes wrong, why it costs you and what to change, in order.
Book a trial class
There are 3 errors in your form.
Full name
Phone
Date of birth
Home address
How did you hear about us?
Message
- The button says Submit.Quick fixWhy it matters: People can’t tell what happens next, and some stop here.The fix: Name the result: “Book my trial class”.
- Seven questions, three needed.Small changeWhy it matters: Every extra field loses people, on a phone most of all.The fix: Ask for a name, a phone number and a preferred day. The rest can wait for the call.
- Mistakes show up only after sending.Needs your developerWhy it matters: People fill the form in twice, and some give up.The fix: Check each field as it is filled in, and say what is wrong next to it.
This is a sample gym app made up for this example. Real reviews use your own screens.
What we check
Four checks, one list of fixes. How people move through it, what each screen asks of them, and where the words and forms get in the way.
Screens
Every key screen, checked for layout, clarity, contrast and how it works on a phone.
Words and forms
Labels, buttons, error messages and forms: what slows people down or makes them give up.
Consistency
Colours, type, buttons and spacing across screens, and whether a design system would save your developers time.
What you get
- A short report, in plain words
- What to fix first, in order, with examples
- Each finding marked on the screen it belongs to
- A call to walk your team or developers through it
- A fixed quote, only if you want us to make the changes
How it works
Four steps, no surprises. A short call to start, a walkthrough at the end, and a fixed quote only if you want us to make the changes.
Ask
Tell us what you have built and who uses it. We reply within one working day with a fixed quote.
Kick-off call
We agree on your users, the tasks that matter most, and access to the site, app or a test version.
We review
We go through it on desktop and phone, task by task. You carry on with your work.
Walkthrough
We walk your team or developers through every finding and the order to fix them in.
Every finding comes with the screen, the reason and the fix.
Ask for a review
Tell us what you’ve built. We reply within one working day with a fixed quote.
If a review isn’t the right first step for you, we’ll say so, and tell you what is.
Prefer WhatsApp? +961 3 266 572Questions
About UX/UI reviews. What we need from you, how long it takes, and what happens after.
See all questionsWhat do you need from us?
A short kick-off call, a link to the site or app (or a test version if it sits behind a login), and the tasks your users most need to finish. Questions your support team hears often help too.
Can our own developers make the changes?
Yes. Every finding shows the screen, what goes wrong, why it matters and what to change, written so your developers can work from it. If you would rather we made the changes, we give you a fixed quote.
Do you review apps and dashboards, or only websites?
All of them: websites, phone apps, web apps and dashboards, live or about to launch. We go through each one on a computer and on a phone.
How long does a review take?
It depends on how many journeys and screens there are. We agree on the three to five tasks that matter most at the kick-off, and your fixed quote gives you the date of the walkthrough.
Is a review the same as user testing?
No. In a review, we go through your product the way a new user would and check every key screen for clarity and ease of use. User testing watches your real users try it. A review is quicker and finds the problems that slow most people down, while testing shows how your own users behave. If you need testing as well, we'll tell you.
What if we have no design system?
That is common. We note where colours, type, buttons and spacing differ between screens, and tell you whether a design system would save your developers time. If it would, we can design one.