Skip to content
IGNARA

ALL MISSIONS

MISSION FILE // STG-04 · UI/UX DESIGN

Design that survives contact with users.

Research, flows, and a complete UI system in Figma — tested on real users before anyone writes code, and specced so developers never guess.

  • PROTOTYPE BEFORE CODE
  • TOKENS FROM THE FIRST FRAME
  • DEV-READY SPECS INCLUDED

00 / TELEMETRY

What's moving in product design.

The currents worth steering by — and what they change about how this mission gets flown.

Design systems ate the deliverable

Clients stopped buying screens and started buying systems — tokens, components, and rules that keep screen forty-one consistent with screen one. A folder of pretty mockups without a system is technical debt with good lighting.

AI raised the floor, not the ceiling

Anyone can generate a plausible interface now. What separates shipped products is the part AI doesn't do: research on your users, decisions with reasons attached, and specs a developer can build from cold.

Testing moved before the build

The cheap place to be wrong is a prototype. Watching five real users struggle with a clickable Figma costs a week; discovering the same problem in production costs a quarter.

00 / WHY THIS PAD

What launching from here gets you.

Something clickable every week

You react to a prototype, not a moodboard or a deck. Feedback lands on the real thing while changing it is cheap.

Decisions come with reasons

Every layout, flow, and color choice traces to a user need or a test result. 'It looks nice' is not an argument on this pad.

Handoff without the guessing

Redlines, tokens, states, and edge cases documented. If this studio also builds it, the design was born build-ready.

Designed by someone who ships

The designer here writes production code the rest of the week. Nothing gets drawn that can't be built on budget.

START IGNITION

00 / FLIGHT PLAN

How this mission flies.

  1. T-4RESEARCH

    Who uses it, what they're trying to do, where the current thing fails them.

  2. T-3FLOWS

    The paths through the product, argued about cheaply — boxes and arrows before pixels.

  3. T-2SYSTEM

    Figma with design tokens from the first frame; a clickable prototype meets real users.

  4. T-1HANDOFF

    What survives testing becomes redlines, specs, and docs any developer can run with.

00 / QUESTIONS

Asked before most launches.

Do you design things you don't build?

Yes — the handoff package is built for any competent developer, not just this studio. Plenty of missions are design-only; the specs are the product.

What if we already have a brand?

Then it becomes tokens and the system extends it instead of fighting it. No rebrand gets smuggled in through a UI project.

How long does it take?

2–5 weeks depending on surface area — a signup flow is not a whole product. The brief scopes it honestly before you commit.

What do we get if we stop after design?

Everything the next builder needs: the Figma system, tokens, flows, the tested prototype, and specs written to be built from. Taking it to your own developers is a normal ending, not a breakup.

00 / COMMS

One email starts the countdown.

Send one screen you're unsure about. The read comes back honest.