Lucas Josefiak

In this talk, I’ll share the key lessons learned after supporting over 2000 Flutter teams in building their own design systems using Widgetbook. You’ll discover practical insights into what makes design systems succeed or fail in real-world teams – from establishing ownership and ensuring designer-developer alignment, to leveraging live previews, documentation, and scalable workflows. Whether your team is starting out or refining an existing system, these lessons will help you avoid common pitfalls and build a design system that actually drives consistency, speed, and product quality.

Design systems promise consistency, speed, and scalability—but turning that promise into a real, working system is a team sport. In this roundtable, we’ll share experiences and challenges around building and using design systems in Flutter projects. We’ll explore how cross-functional collaboration, clear workflows, and the right tooling (from Figma tokens to Flutter components) can streamline development, reduce rework, and even reduce environmental impact by cutting down delivery cycles. Whether you’re starting your design system or scaling one across multiple products, this is your space to trade insights, strategies, and pitfalls to avoid. What are the biggest blockers you've encountered when trying to align design and development teams around a shared system? How are you connecting Figma (or other design tools) to your Flutter codebase—and how automated is that handoff? What are the trade-offs between centralizing control in design vs. letting devs lead on component implementation? Have design systems helped your team move faster—or did it initially slow things down? What’s one feature (like dark mode or accessibility) that a design system helped you deliver more efficiently—and how?