Latest / The Feed & The Thread / The Feed & The Thread - July 14, 2026

Transcript

The Feed & The Thread - July 14, 2026 · The Feed & The Thread

• 0:00
  The screen is becoming obsolete. So where does the interface go?
• 0:03
  It moves to an AI orchestration layer that connects intent
• 0:06
  directly to execution. We need to talk about what remains.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  Chicago Camps. Leadership By Design is on Thursday and
• 0:18
  Friday, September 17 and 18 and tickets are available now! And
• 0:21
  while you're at it, get caught up on UX fundamentals with five
• 0:24
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:26
  available online at feed and thread dot com to submit your
• 0:29
  feeds, or download our app for all the feeds and threads
• 0:31
  delivered right to your pocket.
• 0:40
  The interface is disappearing, yet the work of design isn't
• 0:43
  vanishing. It's moving deeper into the logic of systems,
• 0:46
  demanding we manage flow and perception rather than just
• 0:50
  pixels. Adrian Levy at UX Design.cc makes this case in "AX
• 0:53
  is just the orchestration layer", arguing that AI is the
• 0:56
  new orchestration layer between intent and execution. The
• 0:59
  visible UI work hasn't disappeared; it has shifted down
• 1:03
  into the structure of AI interactions. Designers must now
• 1:06
  focus on orchestrating complex backend processes instead of
• 1:09
  static visual elements. This marks a move from pixel-perfect
• 1:13
  design to managing information flow and decision-making within
• 1:16
  AI systems. Usman Writes at UX Planet explores this tension in
• 1:20
  "The One UX Decision That Makes Your App Feel 10x Faster Without
• 1:23
  Touching a Single Line of Backend…", showing how perceived
• 1:27
  performance matters more than actual backend speed. Every
• 1:30
  loading state evokes specific emotional responses, ranging
• 1:33
  from frustration to confidence. Designers can't opt out of these
• 1:37
  moments and must intentionally craft loading experiences to
• 1:40
  manage user expectations. Good UX focuses on the psychological
• 1:44
  aspect of waiting to make an app feel faster without touching
• 1:47
  code. Other articles today from UX Design.cc on design
• 1:50
  leadership speed and UX Planet on Claude Code skills.
• 2:01
  Designers are trading pixel- perfect layouts for system logic
• 2:04
  today. The interface is fading into the background, yet the
• 2:07
  work is getting harder, not easier. We're moving deeper into
• 2:10
  the mechanics of flow and perception. Over on
• 2:13
  r/UI_Design, a ticketing app designer is stuck on a seemingly
• 2:16
  simple inventory overview. They need to show bundle counts
• 2:19
  versus individual ticket totals, and the layout keeps failing
• 2:23
  them. This isn't just a spacing problem. It's a logic problem.
• 2:26
  When data structures get complex, the UI has to translate
• 2:29
  that complexity into clarity. The friction here reveals where
• 2:32
  design actually lives now. It's not in the corners. It's in the
• 2:36
  reconciliation of conflicting data points. Another designer
• 2:39
  asks how others create those polished UI motion videos. They
• 2:42
  wonder if AI is automating the presentation layer or if there's
• 2:46
  a hidden professional tool. This curiosity highlights a shift in
• 2:49
  how we sell our work. The visual proof matters more than the
• 2:53
  static mockup. But when the presentation becomes a black
• 2:56
  box, we risk confusing spectacle with substance. The skill isn't
• 2:59
  just making it look good. It's making the interaction logic
• 3:02
  feel intuitive. In the same community, someone debates using
• 3:06
  an AI-suggested colorful design for a social platform or
• 3:09
  sticking to a familiar Discord- like interface. They want unique
• 3:12
  branding but fear breaking user mental models. This is the
• 3:15
  tension of modern design. We want to stand out, but we also
• 3:19
  need to be usable. Familiarity reduces cognitive load. Novelty
• 3:22
  builds brand identity. The challenge is balancing those two
• 3:25
  forces without sacrificing function for flair. A focus app
• 3:28
  designer proposes a word-based dial instead of numeric timers.
• 3:32
  They want to replace guilt with comfort by using labels like
• 3:35
  breath, focus, and rest. This moves time selection from a
• 3:38
  setting to a choice. It's a small change, but it shifts the
• 3:41
  user's relationship with productivity. Design isn't just
• 3:44
  about efficiency anymore. It's about emotional regulation. And
• 3:48
  that requires managing perception, not just pixels.
• 3:50
  Finally, a post asks for feedback on a design that
• 3:53
  "doesn't look right" but includes no image. The thread is
• 3:56
  silent because the problem is invisible. This is a reminder
• 4:00
  that context is everything. We can't fix what we can't see. And
• 4:03
  in a field moving toward systemic design, clarity of
• 4:06
  problem statement is just as critical as the solution itself.
• 4:09
  The interface is disappearing, but the responsibility for
• 4:12
  meaning is intensifying. We're designing the logic behind the
• 4:15
  curtain, and that demands a deeper kind of precision.
• 4:26
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:28
  & Friday, September 17 & 18. It's an online event, so you can
• 4:31
  join from anywhere in the world! Tickets are free, thanks to the
• 4:35
  generosity of the community! If it's within your budget, you can
• 4:38
  purchase a general admission ticket for only twenty six
• 4:40
  dollars - with limited early bird tickets at only fifteen
• 4:43
  dollars. Get tickets now at Chicago Camps dot org.
• 4:53
  The tension between perceived speed and actual backend
• 4:56
  performance is shifting where we put our effort. Usman's piece on
• 4:59
  loading states argues that emotional regulation matters
• 5:01
  more than raw milliseconds. That connects directly to the
• 5:04
  focus app discussion in the threads. Replacing numeric
• 5:07
  timers with words like breath or rest changes the interaction
• 5:10
  from a setting to a choice. It's not just about making the app
• 5:13
  feel faster. It's about making the user feel calmer. Exactly.
• 5:16
  The interface is disappearing into the orchestration layer.
• 5:19
  Adrian Levy argues AI sits between intent and execution
• 5:21
  now. So the designer's job isn't to draw the button. It's to
• 5:24
  design the psychological bridge that makes the wait feel
• 5:27
  intentional rather than like a delay. But we risk confusing
• 5:30
  spectacle with substance. The thread about motion videos shows
• 5:33
  how easy it's to automate the presentation layer. If we only
• 5:36
  optimize for the feeling of speed without the logic of the
• 5:38
  interaction, we're just building better loading spinners. The
• 5:41
  risk is real. But the opportunity is defining what
• 5:44
  meaning looks like when the pixels are gone. Then we stop
• 5:47
  measuring success by how fast the screen loads. We start
• 5:49
  measuring it by how clearly the user understands why they're
• 5:52
  waiting.
• 5:55
  That's The Feed and The Thread for today. We'll catch you next
• 5:58
  time!