|
|
Hey again π
sizes="auto" for responsive images is boring in exactly the way I love.
Itβs the browser finally having enough context to delete a bit of work you used to have to do by hand.
Plus some interesting ways to get more out of your design meetings.
Enjoy π¦ - Adam at Unicorn Club.
|
|
|
|
Sponsored by 20i
Upgrade to autoscaling WordPress hosting for always-on, always-fast performance, backed by award-winning support. See the difference and try us out for only $1.
Try 20i now β
|
|
|
Let the browser pick the image size when it can.
For lazy-loaded images, sizes="auto" lets the browser wait until it has layout information, then choose the right source from srcset.
The decision becomes much cleaner: keep explicit sizes for likely LCP images near the top of the page, then let the browser handle the messy cards, grids, sidebars, and avatars lower down.
Why this matters: sizes has always forced you to describe layout too early. With lazy images, the browser can measure the rendered slot first and make a better request.
What I'd do: Add sizes="auto, ..." to lazy-loaded responsive images, then keep hand-written sizes for hero or LCP candidates only.
|
|
|
The prototype gets better while everyone is still talking.
Why: Group sessions are much better when people have live preview, shared context, speech-to-text, and taste in the room. The design can be changed while the conversation is still fresh.
Adopt: Try this on the next design review. Start with a spec, keep the preview visible, and let stakeholders react to the thing itself.
|
|
|
Fast review needs logs, scope limits, and human accountability.
Why: Intercom auto-approves 19% of PRs, but the system decomposes review into sub-jobs, blocks large changes, labels every approval, and keeps humans accountable after merge.
Adopt: Before automating review, define the evidence record: intent match, safety checks, test results, labels, and who watches production afterwards.
|
|
|
|
|
Shape:
Great companies are built in hackathons
β
PostHog's best rule is the simplest one: make hackathons a real operating system, not a novelty day with pizza.
Shape:
TBM 418: Campfires, Trails, and Quests
β
Nice metaphor for AI work. Leave trails, gather at campfires, and make the shared context better after the hard bits.
Build:
A Playful Clip Menu with GSAPβs easeReverse
β
Handy little motion pattern for menus and drawers where the user might interrupt the animation halfway through.
Build:
Good designers, bad websites: a proposal
β
Worth it for the designated dissenter idea. Someone has to argue for the person your nice interface leaves out.
Build:
Localization support for web app manifests
β
Small feature, useful payoff. Web app names and shortcuts can now follow the user's language from the manifest.
Build:
Make your app look globally professional
β
The browser has native Intl helpers for lists, display names, numbers, and dates before you invent another half-broken localisation layer.
Shape:
AI Expedition: Competitive UX Audit
β
Good audit shape: scope the comparison, capture evidence, then turn patterns into opportunities instead of screenshots in a deck.
Shape:
10,000-watt GPU meet 40-watt lump of meat
β
Sharp warning about cognitive debt. If speed leaves nobody understanding the code, the bottleneck just moved.
Ship:
The Voice Layer
β
Worth a look if you're building voice AI beyond demos: LLMs, agents, deployments, and what changes when voice becomes the interface.
|
|
|
|
Support the newsletter
If this was useful, here are two small ways to help it travel:
π Forward to your team
π’ Book a Sponsorship
|
|
|
Thanks for reading
Adam from Unicorn Club
Follow me on X or BlueSky
Connect on LinkedIn
|
|
|
|
|
