The Feed & The Thread - June 18, 2026
Show Summary
We explore whether the interface itself is becoming the variable, shifting our focus from drawing static layouts to defining the rules that govern how they assemble. Christine Vallaure’s A2UI protocol and Oliver Reichenstein’s unified navigation model illustrate this move toward adaptive systems, while community debates on r/UXDesign highlight the growing tension between human-centric design and AI-driven automation.
From The Feed
- Search to Navigate (iA Inc) — iA Writer merges search and navigation to match mental models of content location rather than technical file structures.
- A2UI under the hood: Designing for the new era of radically adaptive UI (Christine Vallaure) — A2UI uses AI to assemble screens from component libraries, preserving accessibility and tailoring interfaces to user intent.
- Underdubbed (L. Jeffrey Zeldman) — Zeldman’s tape recording story illustrates how technical limitations and non-linear processes shape creative output more than perfect planning.
From The Thread
- Company says to me years into working there that i can't show anything work related in my portfolio, what do i do? (r/UXDesign) — Corporate bans on portfolio visibility clash with the need to prove expertise in defining adaptive interface rules.
- Confusion about career path. Please give advice ! (r/UXDesign) — Psychology backgrounds provide a foundation for defining human behavior rules, which is more valuable than layout skills in the AI era.
- How much would it cost to hire someone to create a design system that claude could iterate off of for a webapp like youlearn.ai or wisprflow.ai (r/UXDesign) — Design work is shifting from drawing layouts to creating implementation-ready documentation and tokens for AI code generation.
- Infinite scroll or pagination? (r/UXDesign) — The debate reveals that interfaces are becoming variables where content assembly depends on device capability and user intent.
Today's Notable Articles
- While everyone talks about AI, design is gaining power — Karolina Rojek
- The Siren Song of ariaNotify() — Mat Marquis
Today's Notable Discussions
- The new online narrative is that design is where AI won’t work. — r/UXDesign
- Figma admins beware — r/UXDesign
- The state of the UX profession today. — r/UXDesign
- Wrestling with independence vs interdependence in accessibility — r/UXDesign
- User experience, data and product — r/UXDesign
- I’m over AI — r/UXDesign
Transcript
AI is assembling screens from a component catalog. So designers lose control of the layout. It's radically adaptive, but we need to see if the UX holds up.
Welcome to The Feed and The Thread, brought to you by Chicago Camps. Leadership By Design is on Thursday and Friday, September 17 and 18 and tickets are available now! And while you're at it, get caught up on UX fundamentals with five minute UX at five em UX dot com. The Feed & The Thread is available online at feed and thread dot com to submit your feeds, or download our app for all the feeds and threads delivered right to your pocket.
We used to design for static screens, but now the interface itself is becoming the variable. The real work shifts from drawing layouts to defining the rules that govern how those layouts assemble. Christine Vallaure at UX Design.cc makes this case in "A2UI under the hood: Designing for the new era of radically adaptive UI". She introduces A2UI, a protocol where AI assembles screens from a pre-defined component library rather than generating raw code. This preserves accessibility and clean structure, avoiding the messy div soup that unstructured generation often creates. It's a shift from designing for an average persona to tailoring the interface to the user's specific intent in the moment. Oliver Reichenstein at iA argues in "Search to Navigate" that navigation should follow how writers actually think. iA Writer eight merges search, outlines, and file management into one unified view, so you never toggle between modes again. You jump to headings or snippets seamlessly, matching your mental model of content location rather than technical file structures. The app also adopts Apple's Liquid Glass aesthetic, keeping the experience native to the latest operating system. Jeffrey Zeldman shares a personal story in "Underdubbed" about recording an album as a kid. He tried overdubbing instruments on reel- to-reel tape, but the louder drums drowned out the quiet acoustic tracks he laid down first. It's a messy metaphor for creative work, showing how technical limitations and non- linear processes shape the final output. We learn more from the chaos of making things than from perfect planning. Other reads today from CSS-Tricks on ariaNotify pitfalls and UX Design.cc on design gaining power.
There's a quiet shift happening in the community today. We're moving away from static screens and toward defining the rules that govern how those screens assemble. Over on r/UXDesign, a professional with a background in psychology is asking how to pivot into user experience after a long break. The anxiety is real, especially with the rapid advancement of artificial intelligence. But here's the thing. Their consulting experience isn't obsolete. It's actually the foundation for defining those governing rules. The so-what's clear. We need designers who understand human behavior, not just layout tools. In the same subreddit, a designer is debating infinite scroll versus pagination for an emoji database. They prefer the seamless feel of infinite scroll but worry about performance on older devices. This tension reveals a larger truth. The interface is becoming the variable. We're no longer just drawing grids. We're deciding how content assembles based on device capability and user intent. Another post asks how much it costs to hire a designer to create a system specifically for AI code generation. The goal isn't just visual frames. It's implementation-ready documentation that tools like Claude can iterate off of. This is where the real work is shifting. We're moving from drawing layouts to defining the tokens and states that govern assembly. The conversation gets sharper when someone challenges the idea that design is immune to automation. They argue that human design is often synthesis, not creation from nothing. And AI is getting better at that synthesis. This forces us to ask what our unique value is if the tool can reason through tradeoffs. Finally, a B2B designer is frustrated because their company banned them from showing work in their portfolio. It highlights a clash between corporate caution and professional visibility. If we can't show our work, how do we prove we can define those rules? The thread today shows we're trading pixel perfection for systemic clarity.
Chicago Camps is hosting Leadership By Design on Thursday & Friday, September 17 & 18. It's an online event, so you can join from anywhere in the world! Tickets are free, thanks to the generosity of the community! If it's within your budget, you can purchase a general admission ticket for only twenty six dollars - with limited early bird tickets at only fifteen dollars. Get tickets now at Chicago Camps dot org.
Christine Vallaure's A2UI protocol flips the script on accessibility. Instead of generating raw code that often becomes a mess of div tags, AI assembles screens from a pre- defined component library. It preserves structure while adapting to user intent. That's the clean part. But look at the thread where that B2B designer can't even show their portfolio work. If we shift to defining rules for adaptive interfaces, how do we prove we can write those rules if our output is invisible? Exactly. The value shifts from the visual artifact to the systemic logic. You're no longer selling a screen. You're selling the governance of how that screen behaves under pressure. But the community is already arguing that human design is just synthesis. If AI gets better at synthesizing those rules, what's left for us? The judgment of which rules matter. Zeldman's tape story applies here. The drums drown out the acoustic tracks. We need to decide what gets prioritized before the system assembles anything. We stop protecting the pixel and start protecting the constraint. Right. The interface is no longer the deliverable. The logic behind it is. That's The Feed and The Thread for today. We'll catch you next time!