#user-experience

You’ve Designed the Story, But How Does It Unfold?

Why designers need to understand performance, critical paths and what happens before information reaches the screen. The experience we design is only what happens on stage. Behind it, a whole system of dependencies determines when the performance can begin. Back in 2014, I wrote an article about why we put CSS in the head of an HTML document . It explored the browser’s critical rendering path, and how something as seemingly simple as putting CSS directly into a page rather than loading an external stylesheet could affect how quickly that page appeared. At the time, I was working primarily in f

Muzli · EN

The Next UX Problem: What If AI Does Exactly What We Asked, But Not What We Meant?

We wanted AI to save us time. But what happens when it starts making decisions on our behalf? Imagine this. You open an AI assistant and type: “Find me a good hotel for my weekend trip. Compare the prices, check the reviews, and book the best option.” A few minutes later, the AI comes back. It found three hotels, compared their prices, checked their ratings, selected one, and completed the booking. Everything happened without you opening another tab. Sounds wonderful, right? Now imagine discovering that the hotel is 20 kilometres away from the city centre. The AI selected it because it was che

Muzli · EN

How to design transparent AI cost controls

A practical guide to choosing usage units, designing spending limits, and explaining AI costs before, during, and after the work. Every AI response has a price. People often discover it only when a limit hits or a bill arrives. A quick edit and a long-running agent can look almost identical in the interface. One finishes in seconds. The other might read hundreds of files, call external tools, and retry steps along the way. Yet both start with the same button. Meanwhile, AI products keep changing what they charge for: requests, credits, tasks, usage allowances. Showing more technical numbers wo

UX Collective · EN