Skip to content

QIO / Design

Responsive website design

We design interfaces for different screens and input methods, keeping essential tasks readable, understandable and comfortable to complete.

Discuss the task
01

More than a smaller desktop

Responsive design changes content order, information density and the behaviour of navigation, tables, filters and forms. We decide what matters first and keep important actions accessible without precise taps on tiny controls.

02

What we review

  • Line length, type size and contrast.
  • Touch targets, form labels and error feedback.
  • Cards, images, long headings and tables.
  • Menus, dialogs, filters and the on-screen keyboard.
  • Loading and empty states, with appropriate motion.
03

From Figma to a working page

Representative layouts are accompanied by rules for the widths between them: wrapping, stretching, grid changes and image cropping. Browser and viewport checks are needed to validate the implementation; an approved layout alone cannot do that.

04

Our process

  1. Step 1

    Review the audience, journeys and current mobile issues.

  2. Step 2

    Define content priorities and responsive component rules.

  3. Step 3

    Design key screens and complex states.

  4. Step 4

    Provide implementation notes and review the build when included.

05

Cost and scope

Cost depends on template count, complex components, existing desktop layouts and structural changes. Implementation and browser checks are agreed as part of the scope.

Discuss the task
06

Frequently asked questions

Is one mobile layout enough?

A simple page may need one key size plus clear rules. Complex services need component states and intermediate-width checks.

Can responsiveness improve without a full redesign?

Yes, where the current structure and visual system still fit the task. We first distinguish layout issues from journey issues.