UX100

Core·Field notes

UX and design trends in 2026

UX100 · 6 October 2026

These are the patterns UX100 kept meeting while reading the 2024, 2025, and 2026 classes. A trend earns a place here when it changes what a person can finish, and when more than one category arrived at it on its own.

The screen is the last step of a job

The durable products of this period open on the next action, and they keep the rest of the system one layer back. A clinic visit, a money transfer, a contract review, and a home search all used to begin as a map of the company. They now begin as the task the person already has in mind. Navigation still exists. It has stopped being the greeting.

That shift is why so many 2026 winners feel quieter than the products they replaced. Hims starts from a concern a person can name. Wise starts from a balance and a currency. Opendoor starts from buying, with a map and a time, rather than from a brand film about housing. The chrome gets smaller because the job is specific.

Dashboards have not disappeared. They have moved behind a reason to open them. Harvey’s command center is a legal practice looking at its own work, reached after a matter exists. A wall of charts on the first visit is a trend that faded. A summary that appears when the work is already underway is the one that stayed.

The model sits inside the task

Generative tools that lasted stopped presenting themselves as a blank chat with a personality. The useful pattern is a model bound to a corpus, a matter, a lesson, or a contract, with the source of an answer visible beside the sentence. Perplexity answers with the pages it read. Claude is at its best when the thread is a document the person brought. Harvey is a practice tool, so the model is accountable to a file, not to a general conversation.

Design followed that constraint. The composer is short. The answer is structured. Citations, sources, and the next action sit in the same view as the prose, because a paragraph without a place to go is a dead end in a product. The chat transcript is a history, and the product is the decision the transcript supports.

Teams that bolted a chatbot onto an old information architecture got a second product and a support burden. Teams that rebuilt one workflow around a model got a category leader. The difference shows up in the empty state: a good one names the job. A weak one asks the person to imagine a use.

The design work around that model now has its own names. Human-centric AI design keeps the person as the author of the outcome, with a preview before anything is sent or filed. The harness is the boundary: which tools may run, what may be read, how many steps are allowed, and which writes wait for a person. The answer itself is a set of states — streaming, citation, uncertainty, refusal, edit — and memory only helps when the person can see it and delete it. Those four pieces are the AI design notes beside this cross-read.

Evidence is a design material

Trust used to be a badge in the corner. In the current classes it is the layout. GiveWell leads with a recommendation and keeps the cost, the caveat, and the research on the same descent, so a donor can stop at the conclusion or keep going into the method. Axios builds a story so the claim and the “why it matters” are separate objects. A reader can see the seam.

The same material shows up in money and law. A transfer that hides the fee until the last step is a different product from one that prints the fee in the path. A contract tool that only stores files is a cabinet. Ironclad’s category is the lifecycle, which means status, owners, and the next signature are part of the interface, not a report someone exports.

Designing with evidence has a visual consequence. Pages get longer in a controlled way, and decoration gets cheaper. Photography still carries a brand, as it does on Maven and GoFundMe, but the award went to products where the picture never replaces the fact. If a screen cannot survive in text, it is not finished.

Public services met the consumer standard

Government UX stopped being a special case that was allowed to look institutional. GOV.UK taught a generation of services to speak in tasks: a benefit, a licence, a tax. LifeSG carries that idea onto a phone, where a resident estimates benefits, submits a case, and books a facility without learning the org chart. Borger.dk, in the 2024 class, was the same argument in another country. The pattern repeated because the audience did not get more patient.

The craft details are ordinary and decisive. One thing per screen. Words a person would say out loud. Errors that name the fix. A search that understands the service, not the department. These are old rules. What changed is that public teams are shipping them at the same finish as a bank, and citizens now compare the two.

For anyone designing a regulated product, the public-service winners are the reference, ahead of consumer social apps. A hospital, an insurer, and a logistics network all have the same problem a benefits service has: a person with a right or a duty, and an institution that used to answer with a form. The interface is how the institution keeps the promise.

Commerce became a room

Buying online used to be a grid and a cart. The products that moved the category made the grid into a place with time in it. Whatnot is a live sale: a seller, a comment thread, a bid, and a clock, in one frame. StockX kept the catalogue and added the live room beside it, so a marketplace for objects also behaves like a floor. The person is no longer only filtering. They are present.

That changes the designer’s job. Latency is part of the layout, because a bid that arrives late is a broken control. Identity is part of the layout, because a comment without a person is noise. The object for sale has to stay visible while the social layer moves, or the room forgets why it exists.

Quieter commerce learned the same lesson without a livestream. Framer and Shopify, across different years, treat the storefront as something a team can shape and publish, not a template they request from an agency. The trend is authorship. The merchant, the teacher, and the founder are expected to touch the interface, so the tools have to be honest about what will ship.

The design tool and the shipped product converged

Figma remains the place a team draws. Framer is the place a team publishes. The distance between those two used to be a handoff, a specification, and a rebuild. The trend is a shorter distance: components, type, and layout that survive the trip from the file to the URL. When the tool and the site share a vocabulary, design review is about the product, and the argument about spacing happens once.

This is also a writing problem. Labels, empty states, and error text are designed objects. Products that treat copy as a layer added after the frames ship a different personality on every screen. The winners in the design category keep the words in the same system as the components, so a change in tone is a change in the file, not a ticket.

For in-house teams, the practical consequence is headcount and sequence. A designer who cannot see the published page is designing a picture. An engineer who receives a picture without states is inventing the product in the pull request. The tools that won make those two people look at one artifact.

Interfaces left the desk

A large share of new interface work is no longer a laptop on a table. Waymo’s cabin is a screen in a moving vehicle, with an empty driver’s seat as the context. Tesla’s interface is the same class of problem: a person who needs to know what the car is doing, in the time it takes to look. Oura and Whoop put the interface on the body, where a number is only useful if it arrives at the moment a person can act on it.

The design rules tighten. Type has to be readable at a glance and at an angle. Color has to mean one thing, because there is no paragraph of help text at 60 miles an hour. A wearable that alerts for everything trains the owner to ignore it, so the product is the decision to stay quiet. Fitness and automotive winners were chosen on that restraint.

Travel sits next to this. Hopper and GetYourGuide are still phones, but the person is between places, on a bad connection, with a decision that expires. The interface has to finish. A beautiful page that needs a second load is a missed train. Motion, in this sense, is a constraint on weight, on steps, and on how much the product asks the person to remember.

Security and infrastructure became something you operate

Cloudflare has held the cyber security category across the three classes because the product is a control panel for a network a company actually runs. The trend underneath the repeat win is that security UX left the warning dialog. Operators need routes, rules, and a record of what changed. A lock icon is not an interface. A system you can inspect is.

Logistics rhymes with it. ShipBob and FourKites are about seeing goods move and acting when they do not. The screen is a promise about the physical world, so the design has to show exceptions with the same care it shows the happy path. A green dashboard that hides the late shipment is a failure of information design, whatever the brand film says.

Talent products belong in this group for a quieter reason. JobzMall’s repeat in talent and employment is about a person trying to understand a market, not a feed trying to hold a person. An interface that helps someone operate their own search, save a real lead, and come back to it is the same family as an interface that helps a company operate a network. Both replace fog with a next step.

What dropped out of serious product work

A few habits lost their place once the classes were read side by side. Mystery navigation that exists to express a brand. Onboarding carousels that delay the task. Chat windows with no corpus, offered as the whole product. Dashboards that open before there is anything to manage. Motion that plays on every visit and teaches nothing. Each of these can still be found. They are no longer how the leaders explain themselves.

Dark and light themes stayed, and they stopped being a feature announcement. A product is expected to follow the person’s setting and to keep contrast in both. The work is in the tokens, not in a toggle demo. Accessibility followed the same path: it is a constraint on type, target size, names, and errors, applied while the flow is designed. A separate accessibility phase at the end is how teams ship the exception.

UX100 publishes one leader in each category, chosen in Stockholm, with no submission fee. These notes are the cross-read of those choices. They are not a ranking of trends, and they are not a forecast. They are the patterns that already changed the products worth studying.

Questions

What UX and design trends defined 2026?
The patterns that held across the UX100 classes were task-first screens, models bound to a specific job and its sources, evidence designed into the page, public services built to a consumer standard, commerce that behaves like a room, design tools that publish, and interfaces made for cars, wearables, and people between places.
How does UX100 decide which trends to write about?
A trend is included when it shows up in more than one category and when it changes what a person can finish. The notes are a cross-read of the published 2024, 2025, and 2026 leaders. They are not a survey and they do not rank products outside the award.
Where does AI fit in product design now?
The model sits inside a job the person already has, and the person stays the author of the outcome. A harness bounds the tools and waits before a write. The interface has states for streaming, citations, uncertainty, and refusal. Memory is a list the person can see. Perplexity, Claude, Harvey, and the ChatGPT award are the class examples, and the AI design essays go further into the practice.
Are dark mode and accessibility still design trends?
They are baseline constraints. A product is expected to follow the person’s light or dark setting and to design type, targets, names, and errors so the flow works while it is being built. They are no longer presented as a launch feature.