Picture a customer on their phone, trying to book a service or finish a form on your website. Increasingly, that customer isn’t doing the clicking themselves — an AI assistant riding along in their browser is doing it for them, reading the page, filling in fields, and confirming the purchase. That shift stopped being theoretical this June. Within about three weeks of each other, Google shipped an AI agent directly into Chrome for Android, Figma rebuilt its design tool around AI-generated code, and Apple publicly walked back part of a widely criticized redesign. Individually, each is a product update. Together, they describe a fast-moving change in what “good user experience” means, and what it takes to build it.

Your Customers’ Browser Now Acts on Their Behalf

In late June, Google began rolling out Gemini in Chrome for Android to U.S. users on Android 12 and newer devices with at least 4GB of RAM. The headline feature isn’t the chat panel that summarizes articles or answers questions about the page you’re on — useful as that is. It’s “auto browse,” a tool that lets the assistant complete multi-step tasks on a website: booking a parking spot from details in a ticket confirmation, updating a food delivery subscription, filling out a form using information pulled from the user’s Google account. The assistant asks for confirmation before anything sensitive happens, like a purchase, but the browsing and form-filling itself happens without a human tapping through each screen.

This matters for any business with a website, because it means two different audiences now use your site: people, and the software agents acting for them. A page that’s easy for a person to scan but confusing for a script to parse — vague button labels, forms with no clear field names, checkout flows buried behind several unlabeled steps — creates friction for both. Google isn’t alone here either; Chrome’s push follows similar agentic features from other major browsers and AI assistants over the past year, so this is a direction the whole industry is moving, not a one-off experiment.

Design Tools Now Build the Real Thing, Not Just a Picture of It

A few days later, at its annual Config conference on June 24, Figma — the design tool used by most professional UX teams — announced a set of changes that collapse the line between “designing” a screen and building it. The centerpiece is “code layers,” which let a designer turn any layer on the canvas into working, interactive code with a click or a prompt, then flip back and forth between design and code as they iterate. Figma also introduced a full motion timeline for building animations directly in the tool, and expanded its AI agent so it can pull in context from connected apps like Notion, Slack, and GitHub while it works.

The practical effect is that a proposed UX change — a redesigned navigation menu, a simplified checkout, a new onboarding flow — can go from sketch to a clickable, near-production prototype in the same afternoon, instead of waiting for a separate development cycle to find out if it actually works. That’s good news for speed and cost. It also raises the bar on quality control: it is now easier than ever to ship a plausible-looking interface that hasn’t been properly tested with real users, simply because building it got so much faster than validating it.

Even Apple Is Admitting a Design Call Didn’t Land

The third data point is a useful reality check on all this momentum. At WWDC in early June, Apple revised “Liquid Glass,” the translucent interface style it introduced across iOS, iPadOS, and macOS the year before. The original version drew sustained complaints from users about text and icons becoming hard to read against certain backgrounds. Apple’s fix wasn’t a full retreat — it was a new opacity slider that lets each user dial the glass effect toward more transparency or more solid tinting, along with quieter changes to icon shapes and sidebar corners to improve legibility by default.

The lesson isn’t about glass effects specifically. It’s that one of the most resourced design organizations in the world shipped a defaults-only interface, heard from real users that it didn’t work for everyone, and responded by handing over a measure of control rather than simply forcing a single “correct” look. That’s a pattern worth borrowing regardless of your industry: defaults should be good, but the people actually using your product should have a way to tell you — and you — when a default isn’t working for them.

What This Means If You’re Running a Business

You don’t need to chase every one of these developments directly. But this is a reasonable moment to ask your software partner a few pointed questions.

Would our website hold up if a customer’s AI assistant tried to use it instead of a human? That means clearly labeled form fields, sensible button and link text, and checkout or contact flows that don’t rely on visual cues alone to be understood.

How quickly could we test a UX change before committing engineering time to it? Tools that turn a design into working code in minutes make it realistic to validate an idea with a small group of real users before a full build — ask whether that’s part of your current process, or still an afterthought.

Where do our users have a say in how the experience works for them? That could be as simple as adjustable text size, a dark mode toggle, or clearer accessibility settings — small levers that let people fix friction points themselves instead of abandoning your site or app.

The Takeaway

None of this means you need an AI strategy overnight. It does mean the baseline is moving: browsers are becoming active participants in how customers use your site, the tools that build interfaces are collapsing the gap between idea and working product, and even the biggest design teams in the world are learning, in public, that user feedback beats a confident guess. A short conversation with whoever maintains your digital presence about where you stand on these three fronts is worth more right now than a wholesale redesign.

If you’d like to talk through what any of this means for your website or app, reach out to us at info@kodevox.com or visit https://kodevox.com/contact-us/ to start the conversation.

— The Kode Vox Team

Sources and further reading:

• Gemini in Chrome for Android: The Complete Mobile Productivity Guide — Chrome Story (June 20, 2026)
• Bringing the Best of Gemini in Chrome to Android — Google Blog
• Config 2026: New Materials, New Tools and a More Expressive Canvas — Figma Blog (June 24, 2026)
• WWDC 2026: Liquid Glass (and a Rare Apple Concession) — Dr Logic (June 9, 2026)
• Apple Liquid Glass, iOS 27: WWDC 2026 Brings Refinements Developers Must Adopt Today — Tech Times (June 8, 2026)