The AI landscape doesn't move in one direction — it lurches. Some techniques leap from experiment to table stakes in a single quarter; others stall against regulatory walls, technical ceilings, or organisational inertia that no amount of hype can dislodge. Knowing which is which is the hard part. The State of Play cuts through the noise with a rigorously maintained index of AI techniques across every major business domain — classified by maturity, evidenced by real-world adoption, and updated daily so you always know where you stand relative to the field. Stop guessing. Start knowing.
A daily newsletter distilling the past two weeks of movement in a domain or two — delivered to your inbox while the index updates in the background.
Each dot marks the weighted maturity of practices within a domain — hover for a brief summary, click for more detail
AI that generates wireframes and prototypes from descriptions and converts designs into production code. Includes text-to-wireframe tools and Figma-to-code conversion; distinct from design system generation which creates reusable component libraries rather than individual screens.
AI-powered wireframe generation and design-to-code conversion compress prototyping from days to hours, but the practice remains firmly bleeding-edge: increasingly mainstream for design and SMB ideation, yet production scaling at enterprise remains architecturally constrained. June 2026 data confirms further market consolidation and infrastructure maturity. Code and Theory (enterprise creative agency) documented 75% time-to-prototype reduction using v0, with 50%+ deployment timeline compression across cross-functional teams (product, engineering, go-to-market); Apple's Xcode 27 integration of Figma MCP as the first design tool with seamless IDE installation signals platform-level infrastructure integration. Designer adoption continues accelerating: 50% of designers now ship AI-generated code to production, with 89% reporting faster workflows and 91% improved quality. However, the defining tension persists unchanged and sharpen through new data. Mainstream adoption has created a critical production quality paradox: Faros analysis (22,000 developers) shows AI adoption increased throughput 33.7% while bugs per developer rose 54% and incidents per PR rose 242.7%. New Relic data confirms 67% enterprise adoption at 51-75% of weekly code output, yet 78% report production incidents and 1.7x defect multiplier; senior engineers spend up to one-third of their week triaging AI code failures. Accessibility remains a critical unresolved barrier: Figma Sites (new design-to-web product) contained 210+ WCAG violations in demo content, with automated checkers capturing only 15-30% of actual violations. The binding constraint persists: design system preservation, component reuse patterns, accessibility compliance, and code maintainability require explicit design maturity and iterative human refinement at scale. Teams achieving success front-load precision — explicit design tokens, machine-readable DESIGN.md specs, component metadata, iterative conversation-driven refinement — rather than one-shot export.
Vendor ecosystem consolidation and platform-level operationalization continue through June 2026. Figma's Model Context Protocol (MCP) reached GA status (May 29), and June updates extended infrastructure maturity: Figma MCP server gained custom font support and programmatic asset extraction (June 4), enabling design systems to serve as production code backends. Apple's Xcode 27 (June 8) positioned Figma MCP as the first design tool with seamless IDE integration, accelerating removal of handoff friction. Production deployments documented at Halodoc (SwiftUI generation from Figma, 4-hour manual conversion to automated workflow), Sansan (Japanese enterprise shipping AI Company Summary feature via Dev Mode + Code Connect with iterative prompting), and broader enterprise adoption (Google, Lufthansa, Rocket Mortgage, NBBJ via Figma earnings). Code and Theory (enterprise creative agency) documented v0 adoption achieving 75% time-to-prototype reduction and 50%+ deployment timeline compression. Designer Fund survey (906 designers, June 2026) confirms 50% of designers now ship AI-generated code to production, with Claude at 78% adoption and designer satisfaction at 89% faster workflows and 91% improved designs.
Design system maturity remains the critical prerequisite. Infrastructure ecosystem matured around machine-readable design system specifications: DESIGN.md tooling (bergside design-md-figma v1.0 released April 27, TypeUI standard with 725 GitHub stars, design-md-chrome with 1,263 stars) shows production adoption of structured design specs for AI agents. Smashing Magazine's guidance documents the pattern—spec files with component rules, token layers preventing AI ad-hoc invention, and FigmaLint CI auditing. Named examples (Atlassian Carbon, IBM CMS, Nordhealth) confirm this pattern scales. Teams shipping fastest treat design systems as machine-readable data; Halodoc, Sansan, and ecosystem guidance all emphasize design system as prerequisite, not optional.
However, systemic quality barriers and adoption paradoxes now dominate the landscape. Faros analysis (22,000 developers, June 2026) documents: AI adoption increased task completion throughput 33.7% while bugs per developer rose 54% and incidents per PR rose 242.7%—a critical acceleration paradox. New Relic 2026 survey (200 tech decision-makers) confirms 67% enterprise adoption generating 51-75% of weekly code output, yet 78% report production incidents and 1.7x defect multiplier; senior engineers spend up to one-third of their week triaging AI code failures. Accessibility is a documented production barrier: Figma Sites (new design-to-web product at public beta) contained 210+ WCAG violations (33 critical, 7 serious) in Config.new demo, with automated checkers capturing only 15-30% of actual violations. Critical visual quality failures persist: spacing drift, color inconsistency, missing responsive breakpoints, missing interactive states. Designer confidence (89% faster, 91% improved quality) diverges sharply from developer reality: production incidents spike, senior engineer burden increases, and code quality metrics show persistent defects. Market bifurcates: design-to-code requires developer expertise, design system discipline, and explicit accessibility-in-the-first-prompt; prompt-to-product builds requires neither. Mainstream designer adoption is locked; enterprise production scaling remains constrained by accessibility compliance, design system maturity requirements, code quality verification gaps, and the hidden cost of triaging AI-generated failures.
— Figma MCP server (June 4, 2026) enables bidirectional design-to-code with custom font support and programmatic asset extraction, making Figma a viable backend for automated design systems and eliminating prior typography quality gaps.
— Ecosystem analysis of 8 DESIGN.md tools (bergside design-md-figma v1.0, TypeUI standard 725 stars, design-md-chrome 1,263 stars) showing production adoption of machine-readable design specs for AI code generation.
— New Relic study: AI code introduces twice as many critical runtime issues; senior engineers spend up to one-third of week triaging AI code failures—direct evidence of production quality barriers affecting design-to-code tool adoption at scale.
— Named production agencies (Anima 70% automation, Bricxlabs, 925Studios) document 50-70% scaffolding time reduction for teams with mature component libraries; confirms ecosystem maturity and design-system dependency pattern.
— Faros analysis of 22,000 developers: AI adoption increased task completion 33.7% while bugs per developer rose 54% and incidents per PR rose 242.7%—critical quality paradox directly relevant to design-to-code tool reliability concerns.
— Accessibility expert audit of Figma Sites (design-to-web product): Config.new contained 210+ WCAG violations (automated checkers capture only 15-30% actual violations), Practice-type.com had 107+ violations—production-beta quality exposing accessibility as critical unresolved barrier.
— Bytewaves technical tutorial: Figma MCP transforms REST API output into structured LLM context; Code Connect maps Figma components to codebase components; 97M monthly SDK downloads by March 2026 confirms adoption momentum.
— New Relic survey (200 tech leaders): 67% enterprise adoption generating 51-75% of weekly code output; 94% rate AI code higher at review but 78% report production incidents and 1.7x defect multiplier—mainstream adoption with persistent quality tensions.
2023-H1: First-generation design-to-code tools (Locofy, Uizard, Anima) gain traction among non-professional designers. Peer-reviewed research confirms LLM code generation works well for data tasks but struggles with visual-graphical constraints. Indie developer case study shows 70% time savings from design-to-code conversion. Critical assessments highlight workflow limitations including design-development misalignment.
2023-H2: Wireframe generation research advances with WireGen prototype achieving 77.5% improvement over baselines through LLM-based generation from natural language. Second named case study (Mealcraft, UK) validates production Figma-to-code deployments with 70% time savings. Figma reveals internal constraints: only 3% of developers highly trust AI code accuracy; full automation abandoned in favor of "intelligence amplification" approach due to framework diversity and code usability issues. Practice remains dependent on substantial manual refinement despite time savings.
2024-Q1: Multimodal LLMs (GPT-4V, Gemini Vision) show capability gains: Design2Code benchmark shows 49% human parity and 64% superiority over reference code on 484 webpages. Research addresses layout preservation bottleneck (LaTCoder: 66% improvement with chain-of-thought). Vendor ecosystem expands (Builder.io Visual Copilot, Uizard Autodesigner). However, Figma user survey reveals gap between expectations (89% expect impact) and adoption reality (72% report AI plays minor role, <33% proud of shipped features). Deployment concentrated among indie developers; enterprise adoption remains blocked by design-system integration, accessibility verification, and maintainability concerns.
2024-Q2: Dedicated platform adoption accelerates: Uizard reaches 3.2M users with 80% of new UIs AI-generated. Figma doubles down with native AI (text-to-layout) and Dev Mode enhancements at Config 2024. Independent evaluations cement maturity messaging while documenting continued limitations: bachelor's thesis on five leading tools (Locofy, Anima, etc.) shows responsiveness and advanced feature gaps; industry review of 50+ tools confirms speed/ideation gains but persistent generic output and design system integration challenges. Vendor ecosystem solidifies around Locofy, Anima, Uizard, Builder.io, TeleportHQ. Gap between marketing (50-80% time savings) and reality (significant post-generation refinement required) persists, but confidence growing among SMBs and indie developers. Enterprise integration remains blocked by design system semantics, accessibility verification, and code maintainability.
2024-Q3: Vendor ecosystem expands with Visily launching sketch-to-wireframe and template-driven design generation. Practitioner testing confirms sustained pattern: tools generate prototypes rapidly but require extensive refinement for production use. Accessibility becomes documented blocker—expert analysis shows AI-generated code systematically fails WCAG 2.2 AA compliance. Localization gaps persist, particularly for non-Latin languages. Figma-to-code plugin competition intensifies (DhiWise vs. Locofy). Practice stabilizes as mainstream for SMBs and freelancers seeking design acceleration but remains blocked for enterprise by accessibility verification, design system preservation, and code quality concerns.
2024-Q4: Uizard sustains 931K monthly traffic with 10.9% growth from Autodesigner feature; Figma deepens native AI integration (text-to-layout, Dev Mode, Code Connect). Industry-wide adoption metrics peak: 98% of 400+ U.S. designers report AI-changed workflows with 91% positive ROI. Builder.io and platform vendors document persistent tension between rapid generation and code quality; LLM research identifies seven categories of non-syntactic errors in generated code. Ecosystem consolidates around core vendors with differentiation on language support and component generation; enterprise adoption remains blocked by accessibility compliance gaps, design system preservation, and code maintainability concerns.
2025-Q1: Figma launches Code Connect in beta, formalizing design-to-code as platform feature. Builder.io reports 1M Figma plugin installs with enterprise production deployments. However, adoption-trust paradox deepens: 90% of developers use AI code generation but only 3% maintain high trust. Code quality barriers intensify—duplicated code eightfold higher, security vulnerabilities prevalent, and 66% of developers spend more time debugging than automation saved. Real-world enterprise case emerges (Emaar Properties, UAE using Uizard), but constrained by extensive post-generation refinement. Enterprise scaling remains blocked by accessibility, design system preservation, and code maintainability concerns; practice consolidates as mainstream for SMB and freelance design acceleration.
2025-Q2: Figma Config 2025 announces Figma Sites and Figma Make, deepening platform consolidation of design-to-code workflows. Independent practitioner testing confirms v0.dev, Lovable, Bolt, and Replit accelerate prototyping but require heavy manual support; none approach full automation. Fundamental technical limitations emerge: LiveCodeBench Pro benchmark reveals frontier AI models achieve 0% accuracy on hard coding problems and 53% on medium tasks, while practitioners identify critical context gaps (project history, implicit knowledge, temporal memory) blocking autonomous code generation. Enterprise deployment remains confined to prototyping; production scaling blocked by state management complexity, design system preservation, and developer skepticism.
2025-Q3: Designer-developer trust divergence sharpens: only 32% of designers trust AI design-to-code outputs vs 82% of developers using AI tools generally; 42% of companies abandon AI initiatives. UX team adoption rises to 75% for wireframing tasks, but developer sentiment on generated code quality deteriorates—trust falls to 29% among 49,000+ surveyed developers, with 66% spending more time debugging than saving. MIT analysis documents systemic enterprise pilot failure: 95% of 300 analyzed deployments deliver minimal ROI. Independent tooling evaluations (Locofy, Anima, v0, UXPin) confirm tools accelerate prototyping but fall short of production readiness.
2025-Q4: Figma launches native AI wireframe generator within Figma Make, consolidating design-to-code capability into platform. Figma reports 34% of users shipped generative AI applications (up from 22%), but trust remains low: only 32% of designers trust AI outputs vs 68% of developers. Independent 30-day tool testing confirms value for prototyping (3-5 hours reduced to 30-60 minutes) but all tools require extensive cleanup (20-30% post-generation rework). Designer-developer adoption gap widens to 28 points (31% designers vs 59% developers). Practice consolidates as mainstream for SMB wireframing but production scaling remains blocked by trust deficits, accessibility compliance, and design system preservation challenges.
2026-Jan: Vercel accelerates v0 with AWS database integration (Aurora, DSQL, DynamoDB) enabling full-stack app generation; reports agentic pipeline improvements (dynamic prompts, LLM Suspense, autofixers) achieve double-digit success rate gains. Locofy Figma plugin sustains adoption growth (2,192 users Jan 1 to 4,788+ by March). However, project failure rates dominate industry discourse (88% AI agent failures per HyperSense analysis), with RAND/Gartner confirming 80% never reach production. Independent v0 testing identifies trade-offs: React-only output and credit-based pricing unpredictability limit adoption. "Last mile" problem crystallizes—design system preservation and component reuse remain fundamentally unsolved at scale. Practice consolidates as mainstream for SMB/freelance/startup wireframing but enterprise production scaling remains blocked by design system semantics, component duplication, and hidden post-generation refinement costs.
2026-Feb: Figma releases bidirectional integrations (GitHub Copilot MCP server, Codex-to-Figma) enabling code-design workflows; v0 rebuilds as production platform with GitHub integration and database support. AI backend standardization around Claude Opus with reported 20% error reduction. Designer adoption peaks (89% faster workflows, 91% improved designs); video-to-code emerges (Replay showing 40→4 hour legacy modernization gains). Critical risk surfaced: high-fidelity AI outputs may bypass validation phases. Platform consolidation accelerates but "last mile" design system and component reuse challenges persist unchanged.
2026-Mar: Bidirectional design-code workflows operationalized at scale. OpenAI+Figma MCP integration (Feb 26) enables AI to reference design context directly; GitHub Copilot MCP now syncs rendered UIs back to Figma as editable frames, closing the handoff loop. Figma AI wireframe adoption doubled YoY. Independent comparative testing (Mark Rosal) shows tool diversity: Claude achieves pixel-perfect accuracy with semantic preservation; ChatGPT infers broader UX intent; Cursor prioritizes speed. Case study evidence emerges: Tortuga founder documented eliminating design handoff entirely, opening Figma only twice for single product (vs every screen previously), shifting to code-first Claude workflows. Industry reports document 30-60% frontend dev time reduction across leading tools (Anima, Locofy, Builder.io); 68% of developers now use AI code generation daily. Trust remains divergent: designer confidence high (89% faster, 91% improved quality) but developer skepticism persists (29% high trust in generated code quality). "Last mile" challenges—design system reuse, component duplication, semantic HTML gaps, accessibility—unchanged despite workflow streamlining.
2026-Apr: Research breakthroughs and production deployment maturity signals coexist with a sharper critique of systemic quality failures. ICLR benchmark (Figma2Code) reveals fundamental trade-off in multimodal design-to-code: proprietary models (GPT-5, Gemini 2.5 Pro) achieve visual fidelity but generate rigid, unmaintainable code; open-source models generate cleaner, responsive output due to layout-aware generation. Anthropic launches Claude Design (April 2026), integrating design ideation with handoff to Claude Code in a unified product family. Figma GA of use_figma MCP tool with write access enables design system-driven code generation; named enterprise adoption: Uber's uSpec system automates component spec creation across seven implementation stacks. Technical research: DOne framework (schema-guided generation) achieves 3x faster code generation and 10% better design fidelity. Critical failure modes newly documented: UXPin analysis names Figma, Cursor, Claude Design, Bolt, v0, and Lovable as all exhibiting visual drift and component debt when disconnected from design systems; Smashing Magazine documents that 92% of AI codebases contain critical vulnerabilities, code duplication runs 4x higher than human-written code, and role creep forces designers to master engineering simultaneously—labelled the "Rework Tax" draining engineering resources. UXMagic 2026 tool survey identifies the "Div Soup Problem" (semantic HTML failures) as a systemic barrier across 12 leading tools. Real-world testing: Workspace agency finds design-to-code tools ignore existing 200+ component libraries, requiring 90-minute rebuilds; Builder.io confirms agent accuracy depends entirely on team metadata discipline. v0 blocked 100k+ insecure deployments with 100M+ user interactions signalling mainstream but constrained adoption. Design system quality remains the binding constraint—"Design system is the API that allows AI to build your product safely." Designer-developer sentiment divergence persists: 89% of designers report faster workflows (91% improved quality); only 32% trust AI outputs vs 68% of developers. "Last mile" unsolved at scale: design system preservation, component reuse architecture, semantic HTML, and accessibility compliance remain primary barriers to enterprise production scaling.
2026-Jun: Figma MCP reached GA (May 29), solving the core design-fidelity constraint with bidirectional context flow between design systems and AI agents; production deployments confirmed at Halodoc (4-hour manual SwiftUI conversion automated) and Sansan (Japanese enterprise shipping a live AI feature via Dev Mode and Code Connect). Smashing Magazine's June guidance codifies the prerequisite: AI-ready design systems require spec files, closed token sets, and FigmaLint CI auditing — named examples (Atlassian Carbon, IBM CMS, Nordhealth) confirm this pattern scales, and Designer Fund survey data (50% of designers now ship AI-generated code to production, Claude at 78% adoption) signals mainstream designer commitment despite persistent enterprise quality barriers.
2026-May: Market consolidation accelerates with critical credibility signals mixed with documented risks. v0 adoption confirmed at 4M users with AWS case study validating production deployment of React UIs via Vercel CDN and Amazon Bedrock. Figma stock crashes 55% YTD from IPO high ($142.92 to $16.69), signalling market skepticism on design-to-code ROI despite AI feature acceleration (MCP Server noted as most valuable innovation). Figma Q1 2026 earnings disclosed named production deployments (Google, Lufthansa, Rocket Mortgage, NBBJ) with 46% YoY revenue growth and 139% NDR; Code Connect v1.4.5 shipped batch template support and local validation; Code Layers embeds React as a first-class canvas primitive with multiplayer. Lovable crosses $400M ARR but Broken Object Level Authorization vulnerability (May 2026) exposes 1M+ projects' source code, databases, and credentials from user accounts created before November 2025. METR randomized controlled trial documents 39-point perception gap: developers believe AI tools make them 20% faster but actual testing shows 4% slowdown; GitClear analysis reveals code churn jumped from 3.3% baseline to 5.7–7.1% during AI adoption; ByteIota analysis of 470 GitHub PRs shows AI code has 1.7x more issues than human code, 3x higher readability problems, and 8x more performance inefficiencies. CloudBees study (213 enterprise tech leaders) confirms 81% experienced production failures while only 12% have dedicated AI governance. Practitioner consensus crystallizes around two insights: (1) Design-to-code requires disciplined component metadata (Component.md proposal) and iterative refinement via conversation, not one-shot export; (2) market bifurcates into design-to-code (requires developer expertise) vs prompt-to-product (no developer needed). Designer confidence remains high (89% faster workflows, 91% quality improvement); developer skepticism persists despite mainstream tool adoption. Production scaling barriers unchanged: design system preservation, component reuse, accessibility, and maintainability remain primary blockers at enterprise scale.
2026-Jun: Infrastructure maturity and adoption paradoxes sharpen. Code and Theory (enterprise creative agency) deployed v0 achieving 75% time-to-prototype and 50%+ deployment compression, confirming design-to-code production adoption in professional services. Apple's Xcode 27 (June 8) integrated Figma MCP as first design tool with seamless IDE installation, elevating design-to-code to platform infrastructure level. Figma's June MCP updates added custom font support and programmatic asset extraction, enabling design systems as code backends. DESIGN.md ecosystem matured: bergside design-md-figma v1.0, TypeUI (725 stars), design-md-chrome (1,263 stars) confirm production adoption of machine-readable design specifications. Designer adoption continued: 50% of designers ship AI-generated code to production; 89% report faster workflows, 91% improved designs. However, new data surfaces critical adoption paradoxes: Faros analysis (22,000 developers) documented AI adoption raised task completion 33.7% while bugs per developer rose 54% and incidents per PR rose 242.7%—inversely correlated throughput-quality signal. New Relic 2026 survey (200 tech decision-makers) confirmed 67% enterprise adoption generating 51-75% of weekly code output, yet 78% report production incidents and 1.7x defect multiplier; senior engineers losing up to one-third of weekly time triaging AI code failures. Accessibility emerged as documented production blocker: Figma Sites (new design-to-web product at public beta) failed with 210+ WCAG violations in demo (33 critical, 7 serious); automated checkers captured only 15-30% of actual violations. Designer-developer confidence gap persists: 89% designer satisfaction vs persistent production incidents and developer skepticism. Market bifurcation confirmed: design-to-code (requires developer expertise, design system discipline, accessibility-in-the-first-prompt) vs prompt-to-product (requires neither). Designer adoption mainstream and accelerating; enterprise production scaling remains constrained by accessibility compliance, design system maturity requirements, code quality verification gaps, and rising senior engineer triage burden.