Haliviq

Beautiful Design
That Actually Works

A screen can look good and still lose customers at the third step. Haliviq designs web and mobile products in Bangkok starting from how people actually use them: we talk to your users, map the journey, sketch the flow, design the interface in Figma and test it before developers touch it. The result is a product that feels simple even when the subject is not, such as insurance, logistics or a hospital booking system, and a design file your engineers can build from without guessing.

We start by understanding the problem, not by opening a design tool. A typical project begins with interviews and a review of how your product is used today, then moves through user journeys, information architecture, wireframes and an interactive prototype that real users try before any visual polish. Once the flow works, we design the interface in Figma, build the components into a design system so screens stay consistent across web and mobile, and hand developers specs, tokens and assets. Each decision is checked against evidence, so what gets built serves your users and is not a guess dressed up as a mockup.

Capabilities

Key Capabilities

Concrete capabilities we bring to this engagement — not buzzwords.

User Research

Interviews, usability tests and behavioural evidence gathered in Thai or English, so product decisions rest on what users do. You receive personas, journey maps and a ranked list of problems to fix.

UX & Information Architecture

Flows, navigation and interaction design that make complex subjects understandable. We check labels and structure with card sorting and tree testing before anything is drawn in detail.

Prototyping & Validation

Clickable Figma prototypes that people can try, used to test ideas with real users before expensive engineering begins. Changes at this stage take hours instead of sprints.

Design Systems

Component libraries, tokens and documentation kept in Figma and in code, so product screens stay consistent across web and mobile and new features are quicker to design and build.

Visual UI Design

Interfaces that match your brand, read well in Thai and English, and meet accessibility basics. Every screen is designed in its empty, loading, error and success states, not only the happy path.

Developer Handoff

A tidy Figma file with specs, spacing, tokens and export-ready assets, plus a walkthrough with your developers and answers to their questions while they build.

Tools We Use

Technologies We Use

Proven design and research tools we apply where they fit — chosen for the problem, not the trend cycle.

FigmaFigJamStorybookUserTestingMazePrinciple

How We Work

Our Approach

A clear path from problem to production — adjusted per product, never one-size-fits-all.

01

Research

Interviews, evidence and behavioural insight

02

UX Design

Journeys, structure and interactions agreed with you

03

UI Design

Visual language, components and brand fit

04

Prototype

A clickable version that behaves like the real thing

05

Test

Real users try it, we fix it, we check again

06

Handoff

Specs, tokens and a design system developers can use

FAQ

Straight answers about how we design products.

User research, UX and information architecture, interface design, rapid prototyping and design systems. We understand the problem before opening Figma, and every design is validated with real users before development begins, so nothing reaches engineering as an untested guess.

Yes. We run research and usability testing with real users in Thai and English, and we design for Southeast Asian audiences as well as global ones. This matters for the details a generic template misses, such as local payment flows, address formats and reading patterns that differ from Western UX conventions.

Figma and FigJam for design and workshops, Storybook for design systems in code (not just static Figma files), and UserTesting and Maze for research and validation. We choose the toolset around your team's workflow so handoff is smooth, not a file-format migration project of its own.

Yes. We extend an existing design system where it works and build new parts where it does not. Either way the system lives in code with Storybook as well as in Figma, so designers and engineers look at the same source of truth instead of two versions that slowly drift apart.

A focused UX Audit takes 1-2 weeks and gives you a prioritised list of friction points. A full UX/UI project for one product area typically runs 6-12 weeks from research to handoff, depending on complexity and how much existing research we can build on. A complete design system for an organisation with several products usually runs 3-4 months.

Cost follows the number of screens, the depth of research and whether a design system is in scope. A scoped UX Audit generally starts in the low five figures (THB). A full UX/UI redesign for one product typically starts in the mid six figures, and a complete design system with component library and documentation costs several times that. We quote a fixed price per phase after an initial scoping call.

You do, entirely. The complete Figma file, design tokens, component library, prototypes and all exported assets transfer to you on final payment, with no ongoing licence and no dependency on us. We recommend working inside your own Figma organisation from day one, so you have full ownership and edit access throughout the project, not only at handoff.

Yes, on both counts. Accessibility (colour contrast, touch-target size, screen reader support, keyboard navigation) is part of the design process, not a check at the end. Designs that must support both languages are built with bilingual content in mind from the start. Thai text runs longer than English in most UI contexts, so we make layouts that hold up in both, not only in the language we drafted first.

This is the full design practice: research, flows, interface and handoff in one project. User research and rapid prototyping are narrower services for teams that only need one part, such as interviews to settle a decision, or a quick clickable prototype for investors. They can also be added to a design project when you need more depth.

Have a project in mind?

We'd love to hear what you're building.