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: powerful for rapid ideation and early validation, but production handoff remains constrained by design system integration, accessibility compliance, and code quality governance. The ecosystem is consolidating rapidly — Anthropic entered the space in April 2026 with Claude Design integrating handoff to Claude Code, Figma deepened bidirectional MCP workflows enabling code-design synchronization, and Vercel invested heavily in v0 as a production platform. Designer adoption is mainstream (92% report faster workflows, 91% improved quality), and 92% of developers use AI coding tools monthly. The defining tension persists unchanged: generated code requires 20-30% rework for production, 92% of AI codebases contain vulnerabilities, and core architectural problems (design-system preservation, component reuse, accessibility) remain unsolved at scale. Teams achieving success front-load precision — explicit design tokens, component naming conventions, and metadata discipline — rather than free-form prompting. Designers are adopting enthusiastically; production scaling at enterprise remains architecturally constrained.
Vendor ecosystem consolidation accelerated in April 2026 with Anthropic's launch of Claude Design, integrating design ideation and code generation within a unified product family. Figma continues deepening platform lock-in with bidirectional MCP workflows enabling teams to push rendered UIs back to design files, while Vercel's rebuilt v0 platform now blocks 100k+ insecure deployments and has driven 100M+ user interactions with reported $250M investment. Backend standardization around Claude Opus (Lovable, Bolt, v0) continues with 20% error reduction over prior models. Market forecasts project growth from $5.5B (2024) to $18.16B by 2030 (21.9% CAGR), with Locofy Lightning (one-click Figma-to-code) identified as category-defining innovation.
Developer adoption is mainstream: 92% of US developers use AI coding tools monthly with MIT Technology Review recognition of vibe coding as 2026 breakthrough technology. Designer adoption remains strong: 89% report faster workflows, 91% improved quality. However, systematic code quality barriers are well-documented: 92% of AI codebases contain critical vulnerabilities, code duplication is 4x higher than human-written code, and accessibility failures are systemic (AI-generated React defaults to inaccessible div soup without component abstraction). Teams using v0/shadcn or Figma Code Connect paired with design system enforcement achieve 90% pixel-perfect accuracy; teams generating without structured component constraints see visual drift, component debt, and governance erosion within weeks. Agency testing reports successful prototyping speed (14 days to 4 days documented) but identifies persistent production handoff failures: design-to-code tools ignore existing design system components, requiring 90-minute rebuilds using actual components. The "design system is the API" insight has become central: output quality depends entirely on team metadata discipline (explicit annotations, component properties, design tokens). Enterprise deployments remain confined to prototyping; production scaling blocked by accessibility compliance gaps, design system semantics, and code maintainability concerns.
— Ecosystem segmentation analysis: Figma Make outputs developer-ready component code vs Base44 outputs deployed full-stack apps; clarifies that design-to-code requires developer while prompt-to-product does not, defining market bifurcation.
— Critical assessment documenting design system drift in Claude Design, security vulnerability in Lovable (Broken Object Level Authorization), stock market reaction (Figma down 55% YTD to $16.69 all-time low), and realistic limitations of AI-generated design handoff.
— Analysis of AI productivity paradox: code generation tools increase perceived speed but degrade code quality (churn +73%, security flaws in 29% of code); METR randomized trial shows 39-point perception gap between actual performance and developer belief.
— Practitioner workflow guide documenting real Claude Code + Figma adoption pattern, key enablers (iterative loops, context windows, MCP connectors), and human-in-the-loop requirements for production handoff.
— Five-way tool comparison with named early-adopter case studies (Brilliant, Datadog claiming 10× productivity improvements), market data (Figma stock -7%, Lovable $400M ARR), and documented failure modes (METR study showing senior developers 19% slower with AI).
— Official AWS case study documenting v0 reaching 4 million users and generating production-ready React/Tailwind/shadcn UI code from natural language prompts with integration to Amazon Bedrock and Vercel CDN.
— Design systems expert documents specific failures of design-to-code tools (Figma Make, Claude Code, Claude Design) and proposes Component.md specification as source-of-truth layer between Figma and code generation.
— Hands-on feature evaluation showing Figma shipped more AI in 6 months than 3 years prior; MCP Server identified as most valuable, First Draft saves 30–60 min, while Make varies wildly and Figma Make not production-ready for complex apps.