Digital.Services / 2021

01  ·  Design & UX

Customer journeys, information architecture and UI/UX for mobile apps, web apps and digital products.

What this means

UI/UX design at Digital Services means mapping the customer journey before drawing a single screen, then producing the interface that journey needs — wireframes, flows, visual design and a component set the build can be handed straight to.

Most products fail in the gap between what someone imagined and what they actually shipped. We close it by starting with the journey: who arrives, what they came for, and the shortest honest path from one to the other. That map gets argued over before a single pixel exists, because a wrong turn in a flow diagram costs an afternoon to fix and a wrong turn in shipped code costs a sprint.

Then we design against the journey rather than around it. Wireframes first, at the resolution of boxes and arrows, so the structure gets challenged while it's still free to change. Then the interface itself: typography, spacing, states, and a component library that isn't a moodboard — it's built at the fidelity engineering can lift straight into the build, states and all: empty, loading, error, success.

The platform shapes the decisions as much as the brand does. An iOS flow that ignores the back gesture and an Android layout that ignores the system back button both read as wrong to the people using them, even if neither can say why. We design each platform in its own convention rather than porting one design across both and hoping nobody notices.

01 / Deliverables
  • Customer journey maps and user flows
  • Information architecture and screen inventory
  • Wireframes and interactive, clickable prototypes
  • UI design and a reusable component set — including empty, loading and error states
  • Accessibility and platform-convention review for iOS, Android and web
  • Localisation-ready layouts for right-to-left languages and variable text length
Talk about ui/ux design

Questions

About ui/ux design.

Do you design before you write any code?

Yes. Journey maps and wireframes come first, while a change costs an afternoon rather than a sprint. Visual design and the component set come second, once the structure has actually been argued over and settled.

Can you design for a product that already has an engineering team?

Yes. Design and build are separable — we're regularly the design half handing a component set and prototype to a client's own engineers, or the build half taking someone else's designs to native and cross-platform code.

Do you design for Arabic and other right-to-left languages?

Yes. Bazarly ships in Arabic, which means mirrored layouts, right-to-left text flow and icons that still read correctly reversed — not a translation bolted onto a left-to-right design after the fact.

What do we actually receive at the end of the design stage?

Wireframes, an interactive prototype, final UI screens, and a component set with every state accounted for — not just the happy path. That handoff is built to be picked up directly by an engineering team, ours or yours.

Ready to talk about ui/ux design?

Send a paragraph on what you're building — that's enough to start scoping.