Want to grow beyond writing day-to-day UI code? Visit the Flutter GDE booth for 1:1 mentorship on moving from developer to tech lead or architect, making strong technical decisions, validating startup ideas, and shipping your own indie products with Flutter and AI.

Stuck on dropped frames, memory leaks, or slow builds? Walk up to the Flutter GDE booth for 1:1 help with rendering internals, Widget and RenderObject trees, custom DevTools extensions, crash reporting, and CI/CD quality gates.

Flutter has always promised a simple developer experience with its famous slogan, "Everything is a widget." While this abstraction is fantastic for building interfaces quickly, it can create a false sense of security for complex production applications. The core tension lies in the gap between how we write code and how the framework actually executes it: widgets are just temporary blueprints, and treating them as the real UI often hides the invisible layout engines, element structures, and state trees underneath that can cause massive memory leaks and silent performance drops when mismanaged. This roundtable is a deep dive behind the scenes of Flutter’s user interface layer. We will move past basic declarative UI design to discuss the broad architectural realities of how Flutter measures, paints, and updates things on a screen. Join us to share your strategies for working directly with the framework's lower-level systems, optimizing tree reuse, and understanding exactly where your code ends and the engine begins.

Everything may look like a Widget from the developer’s side. This session explores the Flutter that exists underneath. For years, Flutter has taught us one simple idea: “Everything is a Widget.” It’s a great way to learn Flutter — but there is much more happening underneath. This talk goes beyond the Widget tree to explore the core building blocks that actually make Flutter work. We’ll explore: Widgets are descriptions, not the actual UI Widget Tree vs Element Tree vs RenderObject Tree What BuildContext actually represents Where State really lives What actually happens after build() How Flutter creates, updates, and reuses Elements How Key and GlobalKey affect identity How InheritedWidget works beneath the API Why not every Widget creates a RenderObject What RenderObjects actually do Where the Flutter Framework ends and the Engine begins What really happens between runApp() and pixels on the screen