Airports are pouring millions into AI, AR wayfinding, and personalized journeys, yet travelers still skip their official apps in favor of airline apps, booking platforms, or Google Maps.
The article questions whether airports actually need their own apps at all, given that passengers already piece together the journey with other tools.
For designers, the piece is a reminder that a dedicated app must offer something competitors don't — otherwise it will always be an afterthought in the App Store.
(Note: Unfortunately, e-mail and RSS don’t support advanced layouts and features. If the graphics in this article look strange, you may want to read the article in your web browser.) How much revenue is your site losing each month because of unnecessary UX friction? If you are like most ecommerce leaders or UX manag...
Baymard's new Opportunity Sizing Calculator translates UX friction into hard revenue numbers, giving designers a way to turn subjective design debates into business cases executives can't ignore.
The tool draws on 200,000+ hours of ecommerce UX testing across 40+ industries. You plug in traffic plus either Revenue per Visitor or AOV+Conversion Rate, and it projects annual recoverable revenue broken down by UX theme like checkout, mobile nav, or product pages.
Each UX best practice carries an estimated lift based on how often users hit the problem and how badly it kills conversion. Fixes compound with diminishing returns—solving cart issues improves the baseline, so the next fix in checkout is calculated on that improved baseline, not stacked naively.
To stay realistic, the calculator applies revenue caps: 15% lift for conservative, 25% for midpoint, 35% for aggressive scenarios. Even fixing every usability issue won't double conversions, and this prevents inflated ROI promises.
Practical takeaway: instead of saying 'this dropdown confuses users,' you can say 'fixing this checkout issue unlocks $X per year.' That's the kind of language that wins roadmap slots and budget approvals.
Cursor’s 600+ icon set took a year of hand-drawn work, replacing inherited Codicons with a unified system that covers concepts no generic library has, like AI agents and parallel execution.
Two optical sizes do the job: 16px icons with a 1.25px stroke for small UI, and 24px with a 1.5px stroke for larger displays — similar to optical sizing in typefaces.
Icons are built like technical drawings: straight horizontal/vertical/45° segments, rounded corners, closed shapes, simple slashes, and natural proportions (tall things stay tall) to avoid a toy-like look.
The style borrows from monospace aesthetics — lines are extended where possible, and arrows/objects consistently follow the pointer’s bottom-left-to-top-right direction, giving the set one coherent voice.
Practical takeaway: a large icon system needs explicit construction rules and optical adjustments, not just grid alignment — and replacing an existing font without breaking references is a key constraint to plan for.
Productive disagreement is an art: separate yourself from your ideas, as Pixar’s Ed Catmull advises, to avoid taking criticism personally.
Ray Dalio’s framework helps: distinguish above-the-line (big picture) from below-the-line (details) disagreements, and settle the big things first—then defer to expertise on the details.
Do the work required to have an opinion: argue from both sides, ask 'What if I'm wrong?', and use 'red teaming' to stress-test important decisions.
Actually listen to the other side instead of just waiting for your turn to speak—otherwise, you'll repeat yourself and stall progress.
The author finds themselves instinctively reaching for Telegram's Saved Messages instead of their notes app — not because it's more organized, but because it feels better to write: the satisfying spring animation, instant keyboard response, and zero lag even on old devices make capturing a thought effortless.
Classic notes apps are stuck in a 'paper on the desk' metaphor with folders, titles, and colors. That assumes you have time to organize before writing, while real thoughts come in the middle of a walk, a meeting, or a scroll — and anything slower than a message is too slow.
Messengers inadvertently became the ideal note-taking interface because they were engineered for speed: custom rendering engines, spring physics, virtualized lists. This level of polish isn't a luxury — for fleeting thoughts, the interface itself is the function.
The dream is a notes app that feels exactly like chatting with yourself in Telegram — same fluidity, same imperceptible UI — but with the structure that Saved Messages lacks: full-text search, tags, and a feed that never gets buried by social noise.
Practical takeaway: virtual scrolling is non-negotiable for a notes feed. Rendering all notes at once with .map() will stutter past a few thousand; libraries like @tanstack/react-virtual keep the list smooth by rendering only what's visible plus a small overscan buffer.
