Meta Pixel
Service area 04 · Experience & Product Design

Experience & Product Design: UX Research, Prototyping & QA

We research how people will use your product, design the screens they will see, test the ideas as clickable prototypes, and check the finished build before it reaches customers. The work suits new products as well as redesigns of existing websites, apps and internal tools.

Four Design & Quality Services

Available together as one engagement, or individually: for example, design only, for your own developers to build.

UI/UX Research & Design

Understanding who uses the product and what they are trying to do, then planning the structure before any visual styling.

  • User and workflow mapping
  • Review of comparable products
  • Information architecture and navigation
  • Low-fidelity wireframes
UI/UX design details

Prototyping

Clickable prototypes that let you and your users try a product before development money is committed.

  • Interactive prototypes built in Figma
  • Key journeys such as sign-up, enquiry or checkout
  • Feedback rounds before development starts

Product & Interface Design

High-fidelity screens and a reusable design system so every page and app view stays consistent as the product grows.

  • Visual design for web and mobile screens
  • Figma component libraries and design tokens
  • Readable colour contrast and typography rules
  • Hover, focus and interaction state specifications

QA & Functional Testing

Checking that the built product works as designed on the browsers and devices your customers use.

  • Cross-browser testing in Chrome, Safari, Firefox and Edge
  • Phone, tablet and desktop layout checks
  • Form, login and error-state testing
  • Page speed and accessibility checks
QA testing details

Who It's For and What It Solves

Who Usually Needs This

  • Founders who want to test a product idea as a prototype before building it.
  • Product and IT teams redesigning complicated admin tools or portals.
  • Online retailers whose customers struggle to browse or check out on a phone.
  • Development teams that need independent testing before a launch.

Problems It Addresses

  • Users who can't find features or give up partway through a task.
  • Screens that look and behave differently from one page to the next.
  • Layouts that break on some phones or browsers.
  • Bugs in forms, logins or error handling that only appear after launch.

What a Design Engagement Includes

Usually Included

  • User flows and wireframes for the agreed screens.
  • High-fidelity designs and a clickable prototype in Figma.
  • A component library and design handoff notes for developers.
  • Visual checks during the build that the code matches the design.
  • A test log of issues found, retested once fixed.

Worth Knowing Up Front

  • We design with WCAG AA guidelines in mind; a formal accessibility certification is not included.
  • Design-only engagements end with Figma files and handoff documentation for your own developers.
  • Testing covers the browsers and devices agreed at the start of the project.

How a Design Project Runs

Design and testing follow the same overall shape as our wider delivery process.

01

Research & Journeys

We learn what users need to achieve and map the paths they will take through the product.

02

Wireframes

Structural layouts confirm content, hierarchy and navigation before any visual styling.

03

Visual Design & Prototype

High-fidelity screens and a clickable prototype for review and feedback.

04

QA & Verification

We test the built product against the designs across browsers and devices.

What We Need to Estimate the Work

  • Who the users are and what they need to do.
  • The screens or journeys in scope, or the product to be redesigned.
  • Your brand guidelines, if you have them.
  • Whether we'll also build it, or your developers will.
  • For testing: the browsers, devices and features to cover.

Related Work

Questions About Design & Testing

Can we hire you for design only?

Yes. We can deliver Figma design systems, interactive prototypes, exportable assets and handoff documentation for your own engineering team to implement.

Which screen sizes do you test?

Common desktop widths, tablets from 768px to 1024px, and phones from 360px to 430px wide, in iOS Safari, Android Chrome and the major desktop browsers.

Can you test a product another team built?

Yes. We agree the features, browsers and devices to cover, then report issues with clear steps to reproduce them, and retest once they are fixed.

Want a Product People Find Easy to Use?

Tell us what you're designing or redesigning. We'll suggest where research, prototyping or testing would help most.