Figma · 29 May 2026
Figma Make is moving beyond generating standalone prototypes to operating against a team's local codebase through contextual prompting and collaboration, pulling AI code generation closer to production work.
Intelligence Track
29 May 2026
The Brief
Today splits cleanly into two supply-side India travel signals and a heavy AI-tooling cluster, and the connective thread is the same in both: the advantages that used to come from scale are eroding.
On the travel side, IndiGo doubling down on cost discipline and luxury hotels pivoting to domestic affluent demand both point to a market that rewards whoever merchandises Indian-traveler economics best, not whoever has the biggest brand. On the tooling side, Figma Make reaching into local code and Opus 4.8's mixed-but-real gains say the same thing for how we build — feature velocity is becoming a function of workflow, not headcount, which is exactly the lever a leaner team can pull against MakeMyTrip. The team should be thinking about two moves this week: tightening fare-family and premium-domestic merchandising for the demand that's actually growing, and stress-testing whether design-to-code tooling can compress our build cycle before larger rivals use it to compress theirs. Watch the supply side — IndiGo's cost trajectory and inbound arrival recovery — as the tells for whether these are durable shifts or a single quarter's noise.
Figma · 29 May 2026
Figma Make is moving beyond generating standalone prototypes to operating against a team's local codebase through contextual prompting and collaboration, pulling AI code generation closer to production work.
A hands-on early-access review tests Anthropic's Opus 4.8 across coding, design, and strategy work, giving a mixed read on where it meaningfully improves and where it still falls short of the claims.
Why it matters
Stronger frontier models lower the cost for lean product and engineering teams to ship complex features, compressing the velocity advantage that headcount used to buy.
AI product interfaces are at a pre-convention stage comparable to the early web, where established patterns don't yet exist and designers must experiment toward usable norms rather than apply settled best practices.
Why it matters
OTA AI features such as conversational trip planners and chat-based search have no established UX conventions, so product teams should budget for invention and iteration rather than copying mature patterns.
Feature discovery and onboarding break down when users skip text, and the piece lays out patterns that surface new functionality through interaction and placement rather than copy people won't read.
Why it matters
Rolling out new OTA features like fare alerts or revamped booking flows depends on discovery mechanics that work for low-attention mobile users who ignore tooltips and explainer text.