pinomy.

Today’s motion: “This app needs a login screen.”

Make your case

UI/UX

Every screen should be able to defend itself.

Design at Opinomy is the practice of making decisions visible. A good interface explains itself to users; a good design file explains itself to the next person who changes it.

The design sequence

  1. Listen

    Five to eight interviews with real or prospective users, focused on the last time they faced the problem, not their opinion of a hypothetical solution.

  2. Map

    A journey map showing where people start, where they stall and where they give up. Disagreements between what users say and what data shows are marked in pink.

  3. Sketch and argue

    Low-fidelity options, at least two genuinely different ones, each with a written case. We pick together.

  4. Prototype and test

    A clickable prototype tested with real people. We count where they hesitate, not whether they say they like it.

Accessibility, argued in advance

WCAG 2.2 AA is our baseline. In practice that means contrast checked at design time, touch targets of at least 24 by 24 pixels, visible focus states, error messages that say what to do next and motion that calms down when someone has asked their device to reduce it.

We test with keyboard only and with VoiceOver and TalkBack. We write the accessibility notes into the design file so developers do not have to guess.

Visual design with a reason

Typography, colour and layout are chosen to support the task. A dense data tool and a once-a-year booking page need different typographic rhythm, and we will explain the choice in the hand-off notes.

Design systems are built when a product will grow. For a small site, a short style sheet and a page of examples is more useful than a hundred-component library nobody maintains.

Design deliverables, described honestly

You receive research notes, a journey map, the tested prototype, a component sheet with states (default, hover, focus, disabled, error), and a hand-off document. We do not deliver mood boards without decisions attached.

Try the question builder