Skip to content
Tankar Solutions

UI/UX design

Tankar designs the interfaces its engineers build, so the design system, the prototype and the shipped product are the same thing. Design work covers user research, flows, wireframes, clickable prototypes, visual design and a token-based design system, and it can be bought on its own or as the first stage of a build.

Architectural blueprints with drafting pencils and a metal ruler

Design that ships

The most common failure in product design is a beautiful file that never becomes the product. Tankar's designers work inside the pod that builds the product, so the design system is delivered as code and every shipped screen is reviewed against the prototype.

What you get

A Figma library with tokens and components, flows and wireframes for each user role, a clickable prototype for testing, visual design for every screen, and documentation your team can keep using.

Accessibility by default

Contrast, focus states, touch targets and reduced-motion behaviour are design decisions. They are made once in the system and checked on the shipped screens.

Typical engagements

What this service usually produces, as deliverables rather than adjectives.

  • Design system with tokens, components and usage rules, delivered in Figma and as coded components
  • Clickable prototype of a new product for user testing and investor demos
  • Redesign of a SaaS dashboard or admin panel with usability testing before and after
  • Mobile app design for Android and iOS following each platform's conventions
  • Accessibility audit and remediation design against WCAG 2.2 AA

How it runs

The stages this service goes through, and what you see at each one.

  1. Discovery

    Interviews with users and stakeholders, a review of the current product and analytics, and a written scope and estimate within 48 hours.

    The written estimate follows within 48 hours of the scoped call.

  2. Design

    Flows, wireframes and a clickable prototype, reviewed weekly. Usability sessions with real users where the flow carries risk.

  3. Build

    Tokens and components handed to engineers as code, with the designer reviewing every screen as it is built.

  4. Test

    Accessibility checks with axe and by keyboard, and a comparison of the shipped screens against the prototype.

  5. Launch

    Design documentation and the Figma library handed over with usage rules.

  6. Run

    New screens and components added through the same system as the product grows.

Team shape
A designer paired with a project manager, joined by engineers when the design moves to build.

Stack for this service

The technologies this work is usually built on, and why each one is used here.

TechnologyWhy we use it here
Tailwind CSSDesign tokens become CSS custom properties and utilities, so the coded components match the Figma library exactly.
ReactComponents designed once are built once and reused across the product.
axe-core and LighthouseAccessibility is checked on the shipped screens, not just in the design file.

Questions buyers ask

What buyers ask most about this service, answered before the first call.

Tell us what you are building.

NDA on request. Written estimate within 48 hours of a scoped call. Reply within one business day.

Get a proposalContact

Cookies on this site. Necessary cookies keep the site working. Analytics cookies show us which pages help buyers. Marketing cookies measure campaigns on LinkedIn and Meta. Only necessary cookies are set until you choose. We use analytics cookies to see which pages help buyers. Marketing cookies stay off until you opt in. Details are in the cookie policy and the privacy policy.