UI and UX design people can use first time.

UX is the path and what the product does at every point on it; UI is how that path is drawn. Products that lose people are almost always losing them on the path rather than on the drawing, which is why an engagement starts with recorded sessions and a flow map rather than a visual direction. You need both, because a clear path presented badly still stalls, and a handsome screen on a broken path is a more expensive way to fail. Where a budget stretches to one, we say which half is costing you more and start there. That verdict comes out of the teardown rather than out of a preference.

With recordings of real sessions and a map of every state on the flow, before anything is redrawn. Low completion is concentrated at two or three points, and they are rarely the ones the team expects: a document that came back rejected with no explanation, a review step with no status on it, a field that will not take the name as it appears on the licence. We watch people attempt the job, mark where they stop, then fix the states rather than the styling. A redesign that starts from screens usually moves the drop-off somewhere else instead of removing it. The teardown is where this starts, and what you get back is a recording.

Here, with participants recruited in the UAE, in Arabic or English as the participant prefers. The honest constraint is size: a UAE B2B product may have only a few hundred people in the country who genuinely represent its user, so a large panel study is unavailable at any price. Five moderated sessions with the right five people find more than fifty with the wrong ones, and remote research platforms with Gulf panels cover the studies that need more reach. What we will not do is run the study in another market and present the findings as yours. The sample, the recruitment source and the language go into the scope before the research starts.

If Arabic-speaking people will use the product, yes, and it changes more than the transcript. A string that fits in English can run half again as long in Arabic, a full name as written on an Emirates ID may not fit the field a form reserved for it, and the error message is the string that breaks first because nobody proofreads a failure state. Testing in both scripts is what surfaces those before they ship rather than after. Where an engagement does not fund Arabic research, we write that down rather than testing in English and describing the product as bilingual. What the mirrored layout itself changes is settled at website design.

Four things, in this order: the number of flows rather than screens, how many states each flow has to cover, how much research the decisions need, and whether the second script is in scope. A single checkout with four states is a different engagement from an onboarding that eleven screens and a compliance review pass through. Research is the line most often cut, and it is the one that decides whether the rest of the money is spent on the right flow at all. We scope against those four and put the figure in writing before any design work starts.

No, not by default. This engagement ends at a tested prototype, a component library and a spec that states behaviour; turning that into working code is a separate skill and a separate line. Webzenia does both, so the handover does not sit waiting on another supplier, and that half is described at website development. Where you have your own engineers, they receive the spec and a walkthrough of it, and we stay reachable for the questions that only appear during the build. Which half you need is settled on the first call.

No. A marketing site is read; a product is operated, and the difference shows up in the states rather than in the styling. If the screens costing you money are the public pages, the work sits at website design, which also names the conformance level the UAE has set for digital services, WCAG 2.1 Level AA under the National Policy for Digital Accessibility published in March 2024. Inside a product that level lands on the state set: an error a screen reader can read out, a focus order that survives a modal, a status that is announced rather than only coloured. What a visit has to do before it becomes an enquiry is a third question, answered at build a high-converting website, and the emirate-level read of the same check sits at website design and development in Dubai. Briefs arrive describing one of the three and needing another, which is worth settling on the first call.