📓

Apple TV contextual menu positioned over the selected show in a ranked content row

I saw this Apple TV menu and kept thinking about why it feels so clear.

The interesting part isn’t only that the modal is small. It appears directly over the selected show while the surrounding row stays visible. That proximity explains ownership: these actions belong to this item, not the whole screen. The viewer doesn’t have to remember what they selected or reconstruct where they came from.

A modal can still feel disruptive at any size. Keeping it close to the object that triggered it makes the interruption feel local. The remaining test is whether Back dismisses it and restores focus to the same show.

Sponsored TV video layout with video on the left and product cards on the right

I saw this sponsored video layout on TV and kept thinking about why it worked.

The video stays visible on the left while the product becomes a browsable surface on the right. That separation preserves the story that earned attention, then gives the viewer a clear place to explore without turning the entire screen into a landing page.

It feels less like an interruption and more like a temporary mode. The layout is smart. The real test is whether remote focus, product selection, and the return path are just as clear.

Google just added “Created or edited with AI” disclosures to ads across Search, YouTube, and Discover. But the disclosure lives inside the three-dot My Ad Center panel.

That is technically available, but UX is not only about whether information exists. It is about whether people can see it at the moment it changes their judgment. With EU transparency rules taking effect August 2, AI labels are becoming a real interface pattern. The best version should be visible, understandable, and proportional—not buried, alarming, or vague.

The new ChatGPT desktop UI makes it unnecessarily difficult to find regular chats. Chat, Code, and Agents feel like separate products occupying the same app, but the navigation doesn’t explain that model.

I’d make the modes explicit and keep Projects and Recent conversations visible:

💬 Chat | 💻 Code | 🤖 Agents        Search

Projects
• Atlas
• Identity Ledger
• Home Power

Recent
• Finding ChatGPT Chats
• Harvester Research
• ...

One app, three clear modes—without hiding conversation history or making people troubleshoot where their chats went.

I keep thinking about what happens to design systems when the user is not only a person clicking through an interface, but also an agent trying to understand what it is allowed to do.

Traditional design systems gave teams reusable visual and interaction pieces. Buttons, cards, spacing, typography, states, components. But agents need a different layer of consistency: commands, source boundaries, privacy rules, evidence requirements, tool permissions, output contracts, and stop conditions.

That feels like the next version of a design system to me. Not replacing the visual system, but sitting beside it. A product should be legible to people and operable by agents.

Claude’s new reflection dashboard feels like a quiet UX signal.

AI tools are moving past “look what I can do” and into “look at how you’re using me.”

That’s the design problem I care about most right now: not just making tools more capable, but making sure they preserve human judgment while they help.

It connects directly to what I’m exploring with Atlas: behavior-first design, collaboration, and tools that shape attention instead of just producing output.

I’m back

It’s been a while since I've been active in this space, but I want to start to think out loud again.

A lot has changed. I’ve been building, learning, making, rethinking what I want my work to be, and finding my way into a clearer version of the things I care about.

So this is me reopening the door.

More soon.