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.

Foldables are an established Android form factor, not a lab experiment. Galaxy Z lineup is in its 8th generation, and the iPhone Duo ships this October. Foldable expectations now land on every team's backlog. Most Flutter apps still aren't ready. In this session, you'll learn how to: 1. Read hinges, folds, cutouts, and posture on Android with MediaQuery.displayFeaturesOf and DisplayFeatureState (flat, half-open). 2. Build dual-pane patterns with LayoutBuilder and adaptive navigation, following Material 3 guidelines. 3. Keep navigation, state, and dialogs coherent across fold and split-screen with DisplayFeatureSubScreen and anchorPoint. 4. Prepare for iPhone Duo: side navigation, asymmetric safe areas, and the displayFeatures gap on iOS. 5. Test foldable layouts in CI with widget/golden tests and emulators, without a physical device. By the end, you'll have a mental model, patterns, and a testing playbook for apps designed for changing screen shapes, not accidentally resized.