Skip to content
ZARX Technologies

UI/UX Design

Interfaces users understand on first use

We research your users, prototype the key journeys and test them with real people, then deliver a design system your engineers can build from without guesswork.

  • Clickable prototype before any code
  • Tested with real users every round
  • WCAG 2.2 AA accessible by default

Sound familiar?

The problems we hear most

  • “Users sign up, get confused and leave.”

  • “Every screen looks slightly different.”

  • “Developers keep asking what the design is supposed to do.”

Outcomes

What changes for you

  • Key journeys validated with target users before development starts.

  • A design system that keeps every new screen consistent and faster to build.

  • Fewer support tickets and higher completion on your core flow, tracked after launch.

Capabilities

What we build

  • User research

    Interviews, surveys, analytics and competitor review.

    • Interviews
    • Analytics
  • UX audits

    A heuristic review of an existing product, with a prioritised fix list.

    • Heuristics
  • Information architecture & flows

    Journeys, sitemaps and onboarding.

    • Journeys
    • Onboarding
  • UI design

    Web, mobile and game interfaces – HUDs, menus and stores.

    • Web
    • Mobile
    • Game UI
  • Prototyping & usability testing

    Clickable prototypes tested with real users.

    • Figma
    • Maze
  • Design systems

    Tokens, components and documentation for developers.

    • Tokens
    • Storybook

Deliverables

What you walk away with

Everything is yours at handover: in your repository, your accounts and your files.

  • Research summary and personas
  • User flows
  • Wireframes
  • High-fidelity screens for mobile and desktop
  • Clickable prototype
  • Usability test report
  • Design system in Figma: tokens, components and states
  • Developer handoff with specs and assets

Timeline

New product

A typical engagement, week by week. Your plan is confirmed in the Discovery Sprint.

  1. 01

    Week 1

    Research and goals

  2. 02

    Week 2

    Flows and wireframes

  3. 03

    Week 3

    Prototype and first user tests

  4. 04

    Weeks 4–5

    Visual design and a second test round

  5. 05

    Week 6

    Design system and handoff

Technologies

What we build with

We choose the stack that fits your product, not the other way round.

Design
Figma (incl. Dev Mode)FigJam
Testing
Maze
Behaviour data
Google AnalyticsHotjar
Components
Storybook

Ways to start

Pick the size of the first step

Each option has a fixed scope and a fixed quote.

  • 1–2 weeks

    UX Audit

    Best for: A live product users find confusing

    Fixed quote after a free call

    • Heuristic review of key journeys
    • Analytics review
    • Prioritised fix list
  • 2–3 weeks

    Prototype Sprint

    Best for: Testing an idea before paying to build it

    Fixed quote after a free call

    • Key journeys prototyped
    • Tests with real users
    • Findings and next steps
  • 4–8 weeks

    Full Product Design

    Best for: A new product, designed end to end

    Fixed quote after a free call

    • Research, flows and screens
    • Two rounds of user testing
    • Design system and handoff

Right fit

Are we right for this?

Great fit if you…

  • Are about to build and want to de-risk it
  • Have a product users find confusing
  • Are scaling a team that needs one design language

Probably not a fit if you…

  • Want a logo only
  • Want designs with no user input at all
  • Want a template reskin

Quality & security

Standards this work ships with

  • WCAG 2.2 AA: contrast, focus and 24 px+ targets
  • Every key flow tested with real users
  • Designs annotated for all states: empty, loading and error
  • Consistent tokens shared with code
  • Research data stored with consent and deleted after the project

FAQ

Common questions

Something else on your mind? Ask us directly.

What's the difference between UI and UX, and do I need both?

UX is how the product works: the journeys, structure and decisions a user makes. UI is how it looks and feels: layout, type, colour and motion. A beautiful interface on a confusing journey still loses users, and a clear journey with a careless interface loses trust. For a new product you need both; for an existing one, an audit shows which matters more.

How many users do you test with, and where do you find them?

Usually five to eight people per round, which is enough to find most serious usability problems. We recruit from your existing users where possible, otherwise from people who match your target profile through our network or a recruiting panel. Tests run remotely or in person, recorded with consent, and findings are shared after each round.

Can you redesign our product without rebuilding it?

Often, yes. We start with a UX audit to find the changes with the biggest impact, then redesign in stages your developers can ship one at a time – usually the core flow first. A shared design system lets old and new screens sit together while you move over. We only suggest a rebuild if the current structure blocks the fixes.

Do we get the Figma files and own the designs?

Yes. Design work happens in a Figma workspace your company owns, or is transferred to it at handover. On payment, the intellectual property in the designs, prototypes, research and design system is assigned to you. Fonts, icon sets and stock images stay under their own licences, which we list for you.

Can you work with our in-house developers?

Yes. We hand off through Figma Dev Mode with specs, tokens and assets, join your stand-ups or reviews where useful, and answer questions as your team builds. If you use Storybook, we can deliver coded components that match the design system, so design and code don't drift apart over time.

How long does a UX audit take?

A UX audit takes one to two weeks for most products. We review your key journeys against established usability heuristics, look at analytics to see where people drop off, and where possible watch a few real users try the product. You receive a prioritised list of fixes, ranked by impact and effort, that your team can start on straight away.

Let's build

Let's make your product obvious to use.

Tell us what you're making. A founder replies within one working day with next steps, a rough timeline and a budget range.