UX Autopsy

YouTube's mobile redesign, which dropped the dedicated Subscriptions tab from the bottom bar on November 5, is the defendant in this UX design critique, and Grant argues it is a regression that damages muscle memory. Maya defends it as a deliberate product design bet. This is the Tuesday episode for week 46 of 2026 of UX Autopsy.

The hosts also put two more UI changes on the docket: Google Messages' pinned-chats layout and Apple's Health app redesign, which returned in the iOS 27.3 beta after being pulled.

• YouTube's four-item bottom bar and the Subscriptions swipe-down hidden on Home
• The loss of feed filters and the fewer-Shorts option nobody can find
• Google Messages pinned cards with large photos but no previews or timestamps
• Apple Health's mid-beta pull and revival with Apple Intelligence features

You will walk away knowing how to sort any redesign backlash into regression or real bet. Build a simple table that asks who loses, whether it is muscle memory or a business priority, and whether users get an opt-out, then apply it to your own product design work.

This UX Autopsy design critique opens with France 24's interactive state-by-state election map and a hot take: a zero-zero scoreboard over a red-and-blue map is a lie of omission, not a neutral default. It is the Tuesday episode for week 45 of 2026, recorded on Election Day, and a follow-up to the Vote.gov and HealthCare.gov audit.

Maya and Grant also review Al Jazeera's maps-and-charts page and a hypothetical table-only archetype. They ask what comes first, what an uncalled race looks like, and how each UI signals that an early lead can move.

• The zero-zero scoreboard and why it reads as fact
• Plain gray versus a tile label, a distinct texture, or a sentence under the state name
• A lead labeled as expected to move, placed on the number itself
• A small called/not-yet status marker in a table row

Listeners walk away knowing how to apply a core product design rule: design the unknown state first by defining what is unknown, why it moves, and what resolves it, and never use color that implies an undecided call.

The subscription cancel button is the screen on trial in this UX Autopsy episode, and our spicy take is that a retention screen is only a negotiation if the customer can walk away in one tap. Maya and Grant disagree on that, and they leave it unresolved. This is the Tuesday episode for week 44 of 2026, a product design and UI design critique built around New York City's click-to-cancel rule, which took effect October 1, 2026.

• The single "are you sure?" modal: friction or accident guard?
• The phone-only exit, and why it only passes beside a button
• Confirmshaming copy with lopsided accept and decline buttons
• The stacked save flow of offer, survey, second offer and confirm

You will walk away knowing how to audit your own cancel flow with a five-line checklist: same medium, no delay-only steps, a one-tap skippable save offer, non-shaming copy and honest cancellation consequences. You will also see why passing the city test does not guarantee compliance under state auto-renewal laws. Opinions here are design views, not legal advice.

Plex's TV navigation is the benchmark for a genuine UX regression, and calling the backlash "just change aversion" is how product teams stop reading complaints. This Tuesday episode for week 43 of 2026 puts three redesigns on trial in a product design critique from Pixel Audit, asking one question of each: is this a feeling or a measurable problem?

The hosts examine these specific UI elements:

• YouTube's test comment sidebar, with large thumbnails under the player and always-visible comments that raise spoiler and accidental-click concerns
• Discord's mobile gift button, and whether it was moved or only made less prominent next to the + menu
• Plex's left-side navigation, restored after the press-left muscle-memory path was broken
• Android Authority's reporting and Discord's Google Play reviews, and why a share of complaints is not a share of users

Listeners will walk away knowing how to separate change aversion from a true regression, using a seven-item checklist that covers the specific task, step count, harm versus taste, persistence, user exit, and a rollback trigger set before launch. Screenshot a UI that bugs you and tag us, and subscribe for next week's audit.

This Tuesday episode for week 42 of 2026 opens at Vote.gov's state-selection screen, where Maya argues a failed registration form is the worst bounce in product design. Grant counters that these sites are constrained, not lazy. It's a UX and UI design critique of two government flows that peak together: the Nov. 3 midterm election and HealthCare.gov open enrollment, which starts Nov. 1.

• The Vote.gov handoff to state sites, and what a user needs to know the moment they leave the federal site
• A mailed paper-form fallback path, plus sent versus received deadline wording
• HealthCare.gov's two-deadline banner, with two labeled date lines and a start date on the confirmation screen
• Plan-comparison screens under higher premiums, including a repayment-cap explanation as one worked example in dollars

The hosts also cover accessibility basics such as screen-reader announcements and reading order. You will walk away knowing how to design clear handoffs, label every deadline, and build a plan-comparison checklist you can apply in your own product design work.

Figma's credit screen for the design agent and Weave tools, which leave open beta today, is a meter running before you have said where you are going, and Maya argues it deserves the same suspicion as a sketchy client paywall. In this Tuesday episode for week 41 of 2026, Pixel Audit hosts Grant and Maya run a UX and UI design critique of the shared AI credit pool that now covers the agent, Weave and Figma Make.

This product design audit sticks to confirmed facts and says so when something is unpublished. The design elements discussed:

• The pricing page pool per seat, a known wallet size with no per-prompt cost
• The conflict between release notes and the help article on Starter eligibility
• The left-rail and on-canvas entry points and the @-mention flow for tokens and components
• Collaborator-visible chats and how a shared screen can shape behavior

You will walk away knowing how to run the client-paywall test (cost before action, clear balance, escape hatch) on any metered tool, and how to tell a protective pause from a taxing one.

This Tuesday episode for week 40 of 2026 puts OpenAI's DevDay 2026 keynote under a design critique lens, starting with a spicy take: the reported merger of ChatGPT desktop, Codex, and Atlas into one superapp is three mismatched interfaces stitched together, not a real product decision. Grant and Maya work through what's confirmed versus rumored, then dig into specific UI details, including a proposed persistent status bar modeled on location-sharing permissions, a visible off switch for the always-on 'o' agent, the chat-to-Codex-to-dashboard handoff, and OpenAI's own admission that the desktop redesign is 'kind of a mess.'

For anyone doing UX or product design work, this is a case study in evaluating agentic AI before design conventions even exist. Listeners get a practical framework for judging trust and handoffs in new interaction paradigms.

• How to separate confirmed features from speculative leaks before forming an opinion
• Why always-on assistants need different consent patterns than wake-word devices
• A repeatable question for auditing any 'seamless handoff' claim in product design

Screenshot a UI that bugs you and tag us, subscribe for next week's audit, and leave a review if this changed how you look at your own designs.

Netflix's new vertical Clips feed gets put under the microscope in this week's design critique, and the spicy take is simple: shipping an autoplaying, endlessly scrolling format without addressing known motion-sickness complaints is a UX failure dressed up as engagement innovation. This is the Tuesday episode for week 39 of 2026.

Maya and Grant dig into the specific UI choices driving the backlash: the autoplay-on-open feature Netflix quietly removed after it

The iPhone Duo's fold gets graded against the bets Maya and Grant locked before the keynote, and not every prediction survives contact with real hands-on units. This is the Tuesday design critique for week 38 of 2026, and the scorecard is messier than either host expected.

This UX and UI teardown works through four specific design elements: the crease visibility across the inner display, the redesigned Dynamic Island's shape versus its unconfirmed multitasking behavior, Liquid Glass's paper-like texture and whether it actually solves outdoor readability or just looks good on camera, and a right-handed-only ergonomics flaw the hosts admit they never thought to bet on. A quick-fire round also tackles TechCrunch's

iOS 27's new transparency slider in Liquid Glass is getting praised as a fix for last year's contrast complaints, but it hasn't actually been tested against real accessibility standards, and once you run the numbers, the celebration looks premature. Grant and Maya put the feature through an actual UX and UI design critique, checking it against WCAG contrast thresholds instead of Apple's keynote framing.

This product design critique digs into where the fix actually lives in the settings menu, why that placement matters, and what a year of developer forum complaints since iOS 26 reveals about who's been struggling with this all along.

• The Reduce Transparency toggle's three-taps-deep burial versus the mainstreamed 'Tinted' setting in iOS 26.1
• WCAG contrast-ratio math applied directly to Liquid Glass, including Budiu's 'dishonest' critique
• Screen reader and low-vision reports of dizziness from tilted-looking icons on dark wallpapers
• The unsourced 80% accessibility stat and its missing denominator

This is the Tuesday episode for week 37 of 2026. Listeners will walk away knowing how to test a shipped accessibility feature against real contrast standards instead of taking a keynote's word for it.

Screenshot a UI that bugs you and tag us, subscribe so you don't miss next week's audit, and leave a review if this changed how you look at your own designs.