Anton Borries

Among 450 million smartwatch users globally, Apple has the biggest market share of over 20%. Extending your Flutter app to Apple Watch presents a significant opportunity to enhance user experience. This talk will guide you through the process of bringing your app's data to Apple Watches, enabling users to access key information at a glance via dedicated watch apps and customizable complications. We will also take a quick look at Android Smartwatches because afterall Flutter is best when it comes to being cross platform.

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?