⚡ Quick answer: The biggest gap in design today isn’t between fashionable and unfashionable — it’s between what gets discussed and what actually ships. 94.8% of the top million homepages fail accessibility checks, even though everyone talks about inclusivity. Meanwhile 71% of users expect personalisation, and Gartner projects 30% of new applications will run AI-driven adaptive interfaces — up from under 5% two years ago. Innovation right now isn’t a visual device; it’s how far the interface adapts to the person using it.
The word “innovative” in design usually means “looks unusual.” In reality the things that genuinely change products are nearly invisible in a screenshot — they show up in how an interface behaves, not in its static image.
The numbers show how fast this moved: 93% of designers already use generative tools daily, and 73% consider AI collaboration the most influential factor of the year.
It’s worth separating two very different applications that often get conflated. The first is AI as a designer’s assistant: generating variants, suggesting palettes, drafting layouts. That speeds up work but changes the end product very little.
The second is more interesting — AI inside the product itself: an interface that reshapes around a specific user. Different starting screens for a newcomer and an experienced user, prompts appearing exactly where people usually hesitate, menu ordering that shifts by scenario.
That second kind is what Gartner means by 30% of applications running adaptive interfaces. Growth from 5% to 30% in two years isn’t a trend, it’s a change in the baseline.
The data here is unambiguous: 71% of users expect a personalised experience, and companies that do data-driven personalisation well earn 40% more than those that don’t.
For a small business that sounds out of reach, but the basic levels need neither AI nor a large team:
None of that is innovation in the literal sense. It’s basic hygiene many sites still haven’t reached — which is exactly why implementing it produces a visible effect faster than anything more sophisticated.
That 94.8% failure figure matters for practical rather than moral reasons. Accessibility requirements overlap almost entirely with the requirements of good UX.
Sufficient text contrast isn’t only for people with visual impairments — it’s for anyone reading on a phone in sunlight. Clear form field labels help more than screen readers. Keyboard navigation rescues people who simply don’t like reaching for a mouse.
The minimum set that closes most typical problems: text contrast at or above the recommended ratio, labels on every form field, alternative text for meaningful images, a visible focus state during keyboard navigation, and never conveying meaning through colour alone — a red border with no error text explains nothing.
It’s increasingly a commercial question too: large clients and EU tenders already require compliance, and a site without it simply doesn’t pass screening.
Dark mode stopped being a stylistic choice some time ago. On OLED screens it consumes 15-40% less power, and it reduces eye strain during evening use.
The trap is that a dark theme can’t be an inversion of the light one. Pure black with pure white text produces excessive contrast that makes text appear to vibrate. The working approach is dark grey rather than black, muted accent colours, and slightly lighter font weight.
If there’s no capacity for two themes, one done well is better. A half-finished dark mode where some screens stayed light irritates more than not having it at all.
A button that responds to a press. An element that fades in rather than jumping. An indicator showing the system accepted the action and is working.
None of this is visible in a static layout, which is precisely why it drops out of projects: the client approves a picture, and nobody specified behaviour. The result is an interface that looks like the mockup and feels dead.
The primary function of micro-interactions isn’t beauty, it’s feedback. The user needs to know what’s happening: whether the form submitted, whether the file is uploading or frozen, whether the change was saved or lost. Without that people press buttons twice, create duplicate orders, and write to support.
The quietest but most consequential shift of recent years is that products stopped being drawn page by page and started being assembled from components.
The difference is fundamental. A pile of layouts is twenty separate pictures, each existing on its own, where adding a twenty-first requires a designer. A design system is a library of ready blocks with rules for combining them: buttons, cards, forms, error states, spacing, typography.
| Pile of layouts | Design system | |
|---|---|---|
| New page | Designer draws from scratch | Content manager assembles from blocks |
| Changing button colour | Edit every layout separately | One edit in the component |
| Risk of inconsistency | High: five different buttons | Low by definition |
| Upfront cost | Lower | 20-30% higher |
For a five-page site a system is overkill. For a product that will grow for years it pays back by the second dozen screens — which is why large companies invest in it first, before any visual experimentation.
Multimodal interfaces — where you interact with a product by more than a finger — are gradually moving beyond the big ecosystems. Voice search inside an app, gesture control, photo input instead of text.
For most business products this isn’t a priority yet, with one exception: voice search inside a catalogue genuinely helps stores with large product counts, where typing a name is awkward.
More practical right now is making sure basic input works flawlessly. Address autocomplete, the right keyboard for the field type (numeric for phone numbers), recognising a pasted card number that includes spaces. These details affect checkout completion far more than any voice command.
For a long time speed was treated as the developers’ domain: the designer draws, the programmer optimises. That no longer holds, because most of a page’s weight is committed at the design stage.
Decisions a designer makes that can’t be “optimised” later without rework: full-screen video in the hero, three typefaces at two weights each, high-resolution background images on every block, complex shadows and blurs the browser recalculates on every scroll.
The working approach is to build constraints into the design from the start: two typefaces maximum, images sized for the blocks that hold them, animations that don’t block scrolling. A beautiful layout that takes five seconds to load loses to a plain one that takes one and a half — and that’s a measured pattern, not a matter of taste.
Not everything written about is worth adopting. A few cases where fashion conflicts with sense.
Elaborate scroll animation. Impressive in a designer’s portfolio, heavy on speed, and irritating on repeat visits. We covered how speed affects results separately.
Unconventional navigation. A menu that has to be decoded always lowers conversion. Familiar structure is an advantage, not a constraint.
Glass effects on everything. Transparency over a busy background almost guarantees broken text contrast.
The general rule is simple: a trend should solve a user’s problem, not demonstrate the team’s awareness.
The riskiest scenario is redesigning everything at once. A product that was working changes completely, and if the numbers drop it’s unclear which part caused it: new navigation, new palette or new block order.
The working approach is incremental, with measurement. First a hypothesis with a specific number: we expect the new form to lift conversion from 8% to 12%. Then one element changes, not ten. Then a long enough period to accumulate data — a week on modest traffic is almost always too little. Only after that comes the decision: keep, roll back, or try another variant. Without that cycle a redesign becomes a matter of taste, won by whoever insists loudest rather than whoever has data. At Netloria we try to tie every noticeable interface change to a specific metric before work begins — it removes a great deal of argument about shades.
How to read those numbers and how much data you need for a conclusion is covered in our piece on website metrics.
Proper usability testing costs money and time, but the basic problems surface far more cheaply. A few techniques that work for both a site and an app.
The five-user test. An industry classic: most interface problems are found by the first five users. No lab needed — sit down someone who doesn’t know your product, give them a concrete task (“find the shipping cost to Berlin”) and watch in silence. The key rule is not to help. Every moment the person pauses and rereads is a problem found.
The five-second test. Show the homepage for five seconds, close it, and ask: what does this company do and what can you do here. No answer means the first screen isn’t working.
Checking from a phone in awkward conditions. Not at a desk on good Wi-Fi, but outdoors, in sunlight, on mobile data. That’s how a significant share of real users see the product.
These three checks take a few hours and usually yield more than a month of internal discussion. We run them on every project before launch — and almost always find something, even when everyone is confident it’s all obvious.
Most of the above was built for products with millions of users. For a corporate site or a store the priorities differ, and the order runs like this.
First the basics: speed, mobile version, contrast, comprehensible forms. That produces the largest gain for the least money. Then simple personalisation: landing pages matching the traffic source, browsing history, handling repeat visitors properly. And only then, if the task genuinely calls for it, adaptive interfaces and more complex solutions.
Breaking that order is a familiar story we see regularly: a site with elegant animation that takes four seconds to load and has a form with seven required fields.
If you’re thinking about updating the interface of your product or site — tell us what’s working badly right now. We’re a web studio based in Ukraine, and we’ll start with whatever produces results fastest rather than with a list of fashionable techniques.
