Two days, two stages

For years we treated the interface as the wrapping on the product. Inês argues the opposite: the interface is where the product actually happens, and the people who build it should own more of its decisions. With examples from Fieldnote's last three years, on what changed when designers started shipping and engineers started sketching.

Popovers, anchor positioning, view transitions, scroll-driven animation, container queries: a tour of the platform features that replace whole libraries, with the support tables and the fallbacks you still need.

Why the same 300 milliseconds can feel cheap or expensive, and how to choose curves on purpose. Hana shows the easing library her studio uses on every project, and how to hand it to engineers without a spreadsheet.

Error messages, empty states and button labels are read in a hurry, by people who are stuck. Freya on writing for that moment, and on keeping product copy in the codebase where it can be reviewed, tested and translated.

Mateo has rebuilt one design system for three brands without renaming a single token. How to name by purpose rather than by look, when to add a layer, and the one token you should never create.

Central team, federated model or nobody at all? Three people who've tried them all on contribution, funding and saying no, moderated by the Plenar hosts.

Every kilobyte is a design decision someone made, or didn't. Jonas shows how his team turned a performance budget into constraints designers ask for, and the dashboard that made it stick.

Scroll-driven animation is now in the platform. Léa rebuilds a museum's long-read live on stage, first with a library and then with plain CSS, and talks about when scroll should drive anything at all.

Audits find problems after they ship. Kwame on building components that can't be used wrongly: the patterns, the tests and the code review questions that catch issues before a user does.

The best tools get out of the way. Robin on what a decade of building a design tool taught about taste, defaults and the parts of the craft you shouldn't try to automate.

Sunset, sardines and a DJ who promises not to play anything with a drop. Included with every in-person ticket.

Amara's team supports forty product teams in three countries. The components were the easy part. On trust, contribution, saying no kindly, and measuring a design system by the decisions nobody had to make.

Edge functions, regions and caches, explained for people who make interfaces. What actually gets faster, what gets harder to debug, and how to tell the difference before you migrate.

One in three people experience motion sensitivity at some point. Noor shares research from her team's calm-interface work and a practical checklist for motion that respects everyone.

A pipeline that takes variables from the design tool, turns them into tokens, types and CSS, and fails the build when something drifts. Priya open-sources the whole thing on stage.

Nobody reads the docs, until they're good. Darius on writing docs first, testing code samples in CI, and the search box that halved his team's support questions.

Six speakers from the call for proposals, five minutes each. Announced in May.

A real checkout form, volunteered by a partner. Freya rewrites it, Kwame makes it accessible, and the room votes on every change.

A designer and a developer build the same interaction in parallel, then swap. No slides.

The closing keynote: two engineers on the next five years of the web platform, what design engineers will own, and what we should stop doing now.

Thanks, a few numbers and the announcement of next year's dates.