Aujourd’hui, on doit se débrouiller avec des «Oops», «Something went wrong», ou «Vérifiez votre connexion Internet».

Tout est dit.

Un fil permet de suivre la veille à plusieurs, et aussi de trier les publications d'un flux RSS unique.

The UX of handbrake can be improved as I read this feedback

The most innovative and productive companies I’ve worked with had something in common: employees used the company’s products because they wanted to.

That willingness to use the product tells me more about a company than the size of its budget.

A company can hire excellent people and have a convincing plan for the future. But neither guarantees that anyone there will choose the product when they have a choice.

So when I think about what helps a company come up with useful improvements, one of the first things I’d look at is whether its employees choose to use what they’re building.

Graceful degradation is the opposite to progressive enhancement because a pre-determined “perfect experience” is authored then broken down with support testing strategies instead. The problem with that approach is everything can and will go wrong in the browser, so support testing strategies will unlikely never be reached in a lot of cases, which results in a broken, unresponsive user interface.

The final deliverable of a web-based design is on the web, just like the final deliverable of a print design is print. Instead of handing off, designers and developers need to work in collaboration with each other in design implementation with a culture of flexibility.

Blurhash again :)

The author suggest a new previewsrc attribute to replace blurhash.

Notifications are mostly annoying.

Vehicle Motion Cues uses the device's accelerometer and gyroscope to reduce motion sickness felt when trying to use a device inside a moving vehicle.

According to big-S Science, this type of vehicle motion sickness is caused by the eyes staring at a static display while the inner ear feels the car turning, braking, and accelerating. Motion Cues solve this by placing dots around the periphery of the display that move in harmony with the motion of the car. When the car turns right, the dots sweep across the screen to the left; when the car brakes the dots slide forward.

We don't have to follow the trends.

I've started asking clients a simple question when they bring it up. Not to be difficult, just to understand: "Do you actually use chatbots when you visit other websites?"

Simple is the word that keeps coming up. And I've learned that when a client says simple, they don't mean easy to use. They mean not impressive enough.

The pressure isn't really coming from clients anyway. It's coming from the web itself, from a decade of bloated pages, dark patterns, and feature arms races that quietly redefined what a "real" website looks like. Clients are just reading the room. The room is wrong, but they're not imagining it.
The shift might come from users, not decision-makers. It might come when enough people notice that the fast, calm site was easier to use. That they actually found what they came for. That they didn't have to close three things before reading a single line.

I love the notion of “Quiet AI”. These are tools that are mostly invisible, sit in the background, and do small tasks on the user’s behalf. They never scream for attention but happily assist in repetitive, frustrating tasks that can easily be automated or assisted with a smart helper.

Yes because AI is always a tool and not a solution by itself. What should I do as user with a "Magic AI buttons"; rewrite the button as "Add automatic transcription" (with AI powering the feature) and everyone will understand.

The take here is to document how each folder should behave. An AI agent can take care of the rest. Its integration is seamless.

Well unless the AI agent can not reproduce the same behaviors but it's another discussion.

dickover n. : a modal panel, popover, or curtain presented by a website or app, deliberately obscuring its own content to frustrate the user with an unwanted, unnecessary, mandatory interaction; e.g. asking the user to accept “cookies”, subscribe to a newsletter, install the website’s mobile app, agree to terms of service, or anything else that the user couldn’t give two shits about.

Similarly there are the dickbar

Level 1: What they say
Level 2: What they think & feel
Level 3: What they do
Level 4: Why they do it

There is for example different reasons for a cancellation: https://www.linkedin.com/feed/update/urn:li:activity:7140680577552117760/

The wheel of emotions https://uca.edu/bewell/files/2020/11/Feelings-Wheel-Learn-How-to-Label-Your-Feelings.pdf

Observe instead of asking whereas possible: https://www.smashingmagazine.com/2026/05/four-levels-customer-understanding/#observe-and-diagnose-don-t-validate

Practical ways to uncover user needs:

• Exposure hours, when every employee must be exposed to their customers for at least 2 hours every 6–12 weeks.
• Live UX testing, where we invite everyone in the company to join and observe.
• Co-design with users, where we show new features and ask users to rank them.
• Helpdesk insights, where we ask for frequent complaints and questions from the support every 3–6 months.
• Listening in, where we tune in on a customer service call, web chat, or eavesdrop where users hang out.

1. Fixing issues in the design phase is 100 times cheaper

2. Performance impacts user experience

3. Your site has 50 milliseconds to impress your customers

4. Hick’s Law: The cost of overwhelm

   Stakeholders often think “more options” equals “more value.” Psychology proves the opposite. Hick’s Law states that the time it takes to make a decision increases with the number of options available.

5. White space improves comprehension

6. The power of “fake” progress

7. Make your content readable: roper typography, specifically line spacing (leading) and paragraph width, can increase content comprehension and reading speed by up to 20%.

8. Your users only read 20% of your content

9. User testing with 5 people is the magic number

10. The financial ROI of 9 900%

1. Clarity is job #1
2. Interfaces exist to enable interaction
3. Conserve attention at all costs
4. Keep users in control
5. Direct manipulation is best
6. One primary action per screen
7. Keep secondary actions secondary
8. Provide a natural next step
9. Appearance follows behavior
10. Consistency matters
11. Strong visual hierarchies work best
12. Smart organization reduces cognitive load
13. Highlight, don't determine, with color
14. Progressive disclosure
15. Help people inline
16. A crucial moment: the zero state
17. Great design is invisible
18. Build on other design disciplines
19. Interfaces exist to be used

How to make them better. If the UX priority is the advertising or subscription, no doubt there is also clear quickwins.

Country -> Zip -> ...

Autocompletes the user input to avoid errors.

• Use inputmode="numeric" for a ZIP code
• work with autofill and its autocomplete attributes: postal-code, address-line1, country
• country first in case of international addresses

See the service for it: https://api.zippopotam.us/

I really enjoy the examples provided on the page.

Fitts's Law

The time required to move to a target is a function of the target's size and distance from the starting point.

The target such as buttons must be bigger.

HIck's law:

The time it takes to make a decision increases with the number and complexity of choices.

Miller's law:

The average person can hold about 7 (plus or minus 2) items in working memory at any given time

Format the informations correctly (Phone, Card, Social, Serial, Currency)

Doherty Threshold:

Productivity soars when a computer and its users interact at a pace that ensures neither has to wait on the other. The threshold is 400 milliseconds.

I would say "instant" is reach under 200ms

Postel's law:

Be conservative in what you send, be liberal in what you accept.6

The more formats you accept, the less friction people experience. Validate generously, format strictly.