← back

Modern UI in 2026: the research pass before I touched Figma

My boss handed me a vague task. "Build a visual identity for our demos. Something more modern." No persona, no buyer profile, no constraints.

Instead of jumping straight into design, I wanted to answer a different question first: what does modern UI actually mean in 2026?

Because designs without a definition end up preference-based instead of evidence-based. Everyone likes something different, and when the team finally agrees, a team lead vetoes it. Not because of an insight — because they don't like it. The decisions ride on individual taste instead of shared principles.

So the first thing I did was desk research.

Learning 1: Design maturity

Measures how widely design language is shared across a team, not how skilled the designers are.

Colors and fonts matter, but vocabulary the whole team can use is what keeps momentum after launch. The research puts a scale under it — five stages:

Five maturity stages
Chaos
Managed
Defined
Optimized
Adaptive

Vocabulary the whole team shares is what carries a system past Defined.

The Velvetum study (UX/UI Design Tools 2026) shows that a fourteen-designer team's productivity rose 38% when the rest of the organization adopted the same stack and the same protocols.

Learning 2: Build around user intent

Most products are built on static layouts. It works, but it carries friction: the same screen goes to every user regardless of why they came. For fintech that means a user sees the same screen whether they're reviewing their wealth, planning to buy a house, or selling property to reinvest.

UI in 2026 starts from intent. The interface should recognize what the user is trying to accomplish, then show what's relevant.

Arriving with an intentReviewing wealth
Holdings
Cash flow
Property
Tax

Same modules, same slots. The intent decides which one leads.

Google PAIR distinguishes explicit intent (what the user names) from implicit intent (what the system infers from behavior). Both feed the decision about what gets shown first. For a product with no conversational layer, this doesn't mean bolting on a chat. It means designing forms and screens so the system infers intent before the user has to state it.

So we don't need to rearrange the whole dashboard. We can use set patterns with fixed slots — page actions, section actions, filter rows, modal previews — and change which module occupies the lead slot. The structure stays; the emphasis changes.

TraditionalMenu tree
Four hops, and three of them are guesses.
Intent-basedShort route
One intent, one hop. The tree is still there, behind it.

Learning 3: Friction as a feature

For a decade engineers chased instant response on every interaction. Designers in 2026 are deliberately adding delays back in.

Emil Kowalski compared two identical buttons for a high-impact action: one confirms the millisecond it's clicked, the other inserts a short processing animation before the same confirmation. Users overwhelmingly trusted the delayed version.

It's called perceived reliability. For a high-stakes action — authorizing a payment, moving funds, rebalancing a portfolio — the brain doesn't believe a system that responded too fast had time to do the work. Optimistic UI, where you show success instantly and do the work in the background, damages trust in this context.

High-impact actionsshown 4× slower
Instant~50 ms
Confirm payment
Deliberate150–250 ms
Confirm payment

Too fast and the brain doesn't believe the work happened. The window is narrow — under 150ms reads as anxious, over 250ms as broken.

The window is narrow: 150–250 milliseconds. Long enough to register that something happened, short enough that the app doesn't feel sluggish. Below 150ms triggers anxiety; above 250ms feels broken.

Learning 4: Trust is a formula

Stan Vision (Fintech UX in 2026) defines trust in financial products as transparency + consistency + responsiveness. In practice:

Don Norman's three levels frame the rest: visceral (the first-impression reaction), behavioral (pleasure and effectiveness during use), reflective (how it sits with the user afterwards). An interface that only wins the visceral level doesn't last. In a product people open daily, the reflective level is where the relationship lives — by day 30, the user stops re-checking the numbers because the product has been right for a month.

Learning 5: Stylish but minimalist

The Liquid Glass trend has matured. Professional tools now adopt Anti-Liquid Glass: they keep blur and depth as a spatial cue, so a panel visibly floats above the content, but they remove the refractive distortion that hurts legibility in dense interfaces.

Dark mode. It stops being a nice-to-have; in a lot of products it's the default state, with 60–80% of users preferring it (Tubik, Merveilleux). You don't need an all-dark product, but you do need to build with it in mind. One critical detail: never pure black. Absolute black under white text produces halation, where the white glows and bleeds at the edges, so the text reads as blurry.

Color communicates, it doesn't decorate. Surfaces stay neutral, which gives accents meaning. When color is used for communication, users learn to recognize it without thinking. When everything is colorful, nothing stands out.

States work the same way: green positive, red risk. But color is never alone, because a colorblind user can't tell a red −2% from a green +2%, so indicators pair color with a direction arrow. And the meaning has to be consistent to be learnable, which is the semantic layer again: color-action, color-positive, color-critical. The name carries the intent, and the intent holds across every brand on the system.

The bento grid. Asymmetric cards of different sizes are the default dashboard pattern for 2026.

Flat listeverything equal
Portfolio value
Allocation
Recent activity
Risk
Alerts

Same modules, same grid. The flat list makes every row equal; spans let the important one say so.

Learning 6: Draw a map machines can read

AI has moved from generative (producing content) to agentic (executing work).

For an agent to build on a system without breaking its identity, it needs clear design language to know the difference between blue-500 (descriptive) and button-primary (functional). Figma calls this TokenOps: maintaining machine-readable token rules so an AI produces consistent output. Ask an agent for a confirmation dialog and it reads the system's dialog, spacing and color tokens, then ships a component that matches the rest of the product without inventing a single hex value.

TokenOps
Primitive
brand-500
Semantic
color-action
color-link
color-badge
Components
ConfirmSee more →NEW

brand-500 → color-action → button.background
One decision moves through three layers without anyone opening a component file.

The checklist

So that when the redesign gets reviewed, the conversation is about research instead of preference.

  1. A shared design language. Decisions get made with vocabulary the whole team shares — tokens, patterns, intent — not personal taste.
  2. Intent-based design. Screens serve the intent the user arrived with: the explicit one they name and the implicit one inferred from behavior.
  3. Functional motion, not decorative. Every animation creates trust or directs attention.
  4. Trust as a formula. Transparency, consistency and responsiveness in every interaction, working on all three of Norman's levels: visceral, behavioral, reflective.
  5. Stylish but minimalist. Neutral tones, functional depth, glass on chrome and solid backgrounds on data. Color reserved for meaning, never decoration.
  6. TokenOps ready. Semantic tokens as the single source of truth, named functionally (button-primary) not descriptively (blue-500). This is the precondition for an AI building on the system without breaking it.

Sources

The original articles, grouped by what each one is useful for.

Trend roundups — where the field agrees it's moving:

Fintech-specific — what users expect from financial products:

Design systems + maturity — the token-layer story:

AI as teammate — intent and visible reasoning:

Classics and specific references:

More from the blog

See all