AI is rapidly becoming part of the Flutter workflow, but not in the way it is usually presented in conference talks. This is not about adding a chatbot to your app; it is about a deeper shift: AI is starting to behave like a teammate inside the development loop. In this roundtable, we will explore what happens when prompt-based tools step into tasks like UI scaffolding, repetitive coding, test generation, refactoring, documentation, and debugging. We will compare real experiences: where these tools genuinely save time, where they introduce risks or false confidence, and how blindly accepting generated code can actually degrade a codebase instead of improving it. The goal is not to promote AI hype or reject it, but to build a more grounded, shared perspective: how can Flutter teams work with these tools while maintaining speed, critical thinking, and strong engineering judgment?

Everyone knows Flutter Web as “Canvas, bundles, and compromises.” This talk asks a more interesting question: what changes when Flutter Web stops being only a JavaScript story and starts leaning on WebAssembly? Flutter supports building web apps with --wasm, falls back to JavaScript where needed, and can render faster with less jank when multithreading is available. I’ll show what this means in practice: which apps benefit, where browser compatibility still gets messy, how JS interop changes for Wasm-compatible apps, and why package:web and dart:js_interop matter more than many Flutter teams realize. This is not a generic web talk; it is a practical guide to deciding whether Flutter Web is entering a new phase or just getting a new buzzword.