Video summary

The future of ux/ui design

Main summary

Key takeaways

Technology

Video Summary: Future of UX/UI Design (Tech + Product Workflow + Industry Analysis)

The speaker (Mizko) predicts major changes to UX/UI work driven by AI—both in how designers build products and in how they should position themselves professionally/financially.

Four Main Areas Covered

1) Shifting UX/UI Responsibilities (Design ↔ Development Convergence)

The speaker argues UX/UI designers are increasingly expected to contribute to the codebase, not just produce designs.

They cite an industry shift using Figma’s survey results:

  • Developers participating in design: 44% → 60%
  • Designers participating in development: 21% → 41%

The speaker interprets this as designers moving into development more aggressively than the reverse.

Implication: UX/UI roles are blending with engineering work, making “design-only” less common.

2) AI-Driven “Multitasking” Product Development + Shipping Velocity

The speaker claims AI enables teams (even small teams) to build multiple features in parallel.

Example: their app Choppity (described as the “#1 AI video clipper”) reportedly ships 5–10 major updates/features per week with a team of two.

A key workflow concept is parallel development using tooling similar to “work trees”:

  • In their coding environment (they mention “Claude code,” and UI resembling “Cloud Code”), they describe toggling a work tree option to spawn separate “threads/agents/branches” for different features simultaneously.

Implication: Instead of finishing one feature at a time, AI workflows push toward parallel feature execution.

3) The Cost of Commoditization: Velocity ≠ Value

If AI makes development more commoditized (fast feature building), then shipping becomes less differentiating.

They describe a risk of moving faster than customer understanding:

  • They’ve experienced running through their roadmap backlog faster, creating a mismatch between shipped features and what customers actually want.

Their solution: more customer research.

  • Increased user interviews to ensure they build the right features, not just more features.
  • They also emphasize that delivery cadence is now so fast that shifting focus from “how fast” to “what’s right” becomes critical.

They note that shipping multiple features in a day is possible, reinforcing this change in priorities.

4) Figma’s Relevancy (When It Matters vs When It Doesn’t)

The speaker argues Figma’s usefulness depends heavily on organizational context.

They split designers into two types:

  1. Teams where Figma acts as single source of truth for stakeholders, documentation, and sign-offs.
  2. Their own founder-led setup where they control everything and build directly with code.

Their position:

  • In their workflow, Figma is “less relevant right now.”
  • They claim most output happens in Claude Code and code directly, estimating ~10% in Figma and 90% in Claude code.

Workaround to recover UI polish in Figma:

  • Use a Figma Chrome plugin to copy a screen (page or element) from their app into Figma.
  • The copied result allegedly includes editable layouts with auto-layout, allowing them to polish design screens after coding.

Key takeaway: Figma may be crucial for cross-stakeholder environments, but less necessary for solo/founder pipelines that design via coding + AI.

“Million-Dollar AI Trade” (AMD) Tied to the UX/UI Future

Though not a design tutorial, it supports their argument about preparing for AI disruption.

They describe investing in the AI supply chain, focusing on semiconductors (AMD specifically):

  • They felt AI could threaten white-collar work and wanted financial protection.
  • Instead of quitting or complaining, they researched who benefits (data centers, energy, chips).

Reported results include:

  • Over 350% on AMD at some points (with an exit near ~450% referenced)
  • Accumulated nearly 2,000 AMD shares around a ~$60–$120 range (details vary)
  • Claims $1M+ profits total:
    • One account profit mentioned ~$1M+
    • Another batch profit mentioned ~$220k
  • Still holding remaining AMD shares, expecting further growth before selling

Purpose of sharing: “positioning” rather than reacting—benefit from the AI wave even if jobs are disrupted.

“Playing the Victim Card” (Strategic Career Takeaways)

The speaker discourages panic-driven attitudes and offers practical alternatives.

Three takeaways to avoid victimhood:

  1. Use AI for upskilling (example: using AI to research the AI supply chain for investing).
  2. Build an AI company (get “skin in the game”).
  3. Invest in AI companies—including public markets, not only startups (while acknowledging work, risk management, and responsibilities are required).

They conclude they expect AI to act more like a co-pilot than fully replace everyone—while still increasing the number of problems humans solve.

Main Speakers / Sources

  • Speaker: Mizko (primary narrator)
  • External source referenced: Figma survey (used for design/dev participation stats)
  • Tools mentioned: Figma, Claude Code (coding/workflow environment), and a Figma Chrome plugin
  • Other individuals referenced (as examples of AI usage): Marina, Denisa, John
  • Company/app referenced: Choppity
  • Investment/ticker referenced: AMD (Advanced Micro Devices)

Original video