Prompt as self-portrait, De-slopifying your designs, The strategic designerUX Collective
DesignProduct
Three sharp reads: prompting as self-expression, fixing 'AI slop' visuals, and the rise of the strategic designer.
- Prompt as self-portrait: How you prompt an AI reveals your taste and thinking as much as the output does — prompting is becoming a design skill in its own right.
- De-slopifying: Practical fixes for the generic, over-polished look of AI-generated UI and imagery — useful for anyone vibecoding interfaces.
- The strategic designer: A case for designers moving upstream into strategy as AI absorbs more production-level execution work.
- Bottom line: All three point the same direction: as AI handles execution, designers' value shifts toward taste, judgment, and framing.
Amazing glassA new open component library replicates Apple's 'liquid glass' effect pixel-for-pixel in HTML, React, and Vue.
- What it is: Open web components that bend and refract the page behind them, tuned pixel-by-pixel against Apple's own glass rendering.
- Why it matters: Apple's liquid-glass visual language is fast becoming a default 'premium' aesthetic expectation across platforms — now it's portable to the web.
- Design systems angle: Teams chasing a high-end look will reach for this instead of hand-building glassmorphism — expect it to show up everywhere quickly.
A loading state within a loading stateA sharp lesson on how nested loading states quietly make products feel worse, not better.
- The problem: Stacking loading indicators — a spinner inside a skeleton inside a placeholder — is often the 'obvious' fix that actually confuses users more.
- Why it matters: Perceived-performance design is underrated — small sequencing choices change how fast a product feels, independent of actual speed.
- Bottom line: Worth an audit of your own product's loading states — nested ones are a common, easy-to-miss pattern.
Google has the best AI money can buy. Its products still feel broken.Despite top-tier AI, Google's products keep breaking the basic trust contract users expect from them.
- The core issue: The piece argues Google's AI-era products fail not because the models are weak, but because they violate users' old expectations of predictability and control.
- Why it matters: Model quality and product quality are different problems — bolting a great model onto a product doesn't fix broken UX.
- The pattern: It echoes a broader industry issue: AI features ship before the surrounding product experience is rethought to match them.
- Bottom line: A caution for any team shipping AI features fast — users judge the whole experience, not the benchmark scores.
For product
Before shipping the next AI feature, audit whether it breaks existing expectations about predictability and control — that's usually the real complaint, not model quality.