why flutter won?

“Why Flutter Won” looks at how Flutter grew from a new cross-platform framework into a trusted platform. We’ll cover its architecture, early concerns, improvements like Hot Reload, null safety and Impeller, as well as how Flutter performs in real-world production.

Transcript

1. S SA GDE ACADE MY · S E PT E MBE R 3 , 20 2 6 Why Flutter Won How a risky cross-platform bet became a serious production platform Nicholas Gidudu Flutter Developer Yunwen Eric Software Engineer
2. Two developers, two halves of one story Nicholas Gidudu Flutter Developer How Flutter earned developer trust. Yunwen Eric Software Engineer · Founder, Togeva How Flutter earned production trust.
3. The journey 01 02 03 The problem The bet The doubt Cross-platform was hard Own the rendering stack The skeptics had a point 04 05 06 The turning points The production test The next bet Four engineering answers Real users, real devices AI-native interfaces
4. PA R T I — N I C H O L A S The problem and the bet
5. One product, too many platforms Android Four codebases Four teams Four sets of bugs iOS Web Desktop Build once. Reach everyone. Without sacrificing the experience?
6. 20 1 5 · P ROJ E C T S K Y “What if we stopped depending on native widgets and rendered the interface ourselves?” A risky idea — and one that defined almost everything that came next.
7. Don't bridge the UI. Own it. TRADITIONAL F LU T T E R Your code Your Dart code ↓ ↓ Bridge Framework ↓ ↓ Native components Engine ↓ ↓ Screen Pixels Flutter owns the pixels.
8. Three layers, one mental model Framework Widgets · Gestures · Animation Engine Impeller · Dart runtime · Text layout Embedder Android · iOS · Web · Desktop We keep coming back to this diagram.
9. “Why would I bet my product on this?” “The ecosystem is too small.” “Flutter apps are bigger.” “Will it feel native?” “Will Google keep supporting it?” Architecture alone doesn't earn trust.
10. The skeptics had a point App size Platform fidelity The engine adds real overhead. Early widgets weren't always right. Shader jank Plugins First-run stutter was visible. pub.dev had real gaps. The critics weren't wrong. Flutter had to evolve.
11. Objection → engineering response Slow iteration → Hot Reload Runtime null errors → Sound null safety “It's only for mobile” → Six platforms Rendering jank → Impeller Missing plugins → A grown ecosystem 38k → 50k+ packages Not one revolution — a sequence of decisions.
12. TURNING POINT 01 Hot reload changed the feedback loop Edit code → Compile the change → Inject into running app → See it instantly State survives. The widget tree and much of the app's state stay intact across the reload. L I V E D E MO Change a colour. Watch the app keep its place.
13. T UR N I N G P OI N T 0 2 · DART 2 . 1 2 Dart had to grow up too BEFORE Runtime surprise Flutter wasn't the only thing maturing. → AFTER Compile-time error
14. Developer trust, earned ✓ ✓ ✓ ✓ Hot reload Null safety Packages & tooling Declarative UI But could it grow beyond mobile? Eric →
15. THE EVIDENCE Trust, in numbers 171k GitHub stars on flutter/flutter 50k+ packages on pub.dev — up from ~38k in 2023 1.3B pub.dev package downloads in 30 days Figures as of 2026 — worth re-checking before you present. ~2M developers building with Flutter
16. You've probably used a Flutter app this week Google Pay Google Ads Google Classroom payments at national scale advertiser console education Nubank BMW Toyota LatAm digital banking My BMW companion app 2026 RAV4 multimedia system Alibaba Xianyu eBay Motors SNCF Connect marketplace marketplace French rail ticketing Phones, cars, dashboards — shipped, not piloted.
17. PA R T I I — E R I C Beyond mobile
18. TURNING POINT 03 One codebase, six platforms Android iOS Web Windows Same framework × Platform embedder = An application platform macOS Linux
19. One codebase is not one experience So Flutter gives you the seams to branch on. SCREEN SIZE TOU CH VS MOU S E P L AT F O R M F E E L Adaptive layout Input affordances Conditional branch Breakpoint at ~600dp: bottom bar becomes a side rail, one pane becomes two. Hover states, visible scrollbars, keyboard shortcuts — added where the pointer exists. iOS gets Cupertino transitions and switches; Android keeps Material. Same widget tree. LayoutBuilder · MediaQuery MouseRegion · Scrollbar Platform.isIOS · Theme.platform NavigationBar → NavigationRail Shortcuts · Actions Switch.adaptive You branch on capability — you don't fork the app.
20. TURNING POINT 04 Impeller: fixing jank at the root BEFORE WITH IMPELLER Frame needs a shader Shaders prepared ahead ↓ ↓ It compiles mid-render Predictable rendering ↓ ↓ Dropped frame Smoother frames Not just fast — predictably fast.
21. Every frame has a deadline 16.67 8.33 ms per frame at 60 FPS ms per frame at 120 FPS UI thread Raster thread Build · Layout · Logic Paint · Composite
22. PA R T I I I The production test
23. Production changes the conversation DE MO S R UN ON U S E R S H AV E Flagship phones Budget Android devices Fast Wi-Fi Limited RAM, older GPUs Costly, patchy data The user's phone is the real benchmark.
24. Cross-platform is a business decision TRADITIONAL Android team iOS team → Web team How much product can this team ship and maintain? WI T H F LU T T E R One product team Shared features. Shared fixes.
25. Connectivity is part of your architecture UI ↕ Local data ↕ Sync layer ↕ Server Assume the network will disappear. Caching Optimistic UI Local DB Retry queues
26. What production taught us 01 02 03 Test on the phones users own Modularise early Keep heavy work off the UI isolate 04 05 06 Treat app size as a feature Design offline behaviour on purpose Automate visual regression tests Flutter changes which problems you spend time on.
27. PA R T I V The next bet
28. What if screens aren't always pre-built? T R A D I T I O N A L LY I N C R E AS I N G LY Developer writes the UI Intent + context + model ↓ ↓ User sees the UI Adaptive interface ↓ User The widget tree is already composable data.
29. Generate. Orchestrate. Validate. Test. G E N E R AT E O R C H E S T R AT E VA L I DAT E TEST GenUI Genkit Dart Typed models Golden tests Composable interfaces AI flows in Dart Known structures Verify what was generated A declarative UI system, built for years, may have found a new use case.
30. Flutter didn't win overnight THE BET THE EXPERIENCE T H E MAT U R I T Y T H E R E AC H Own the pixels Hot reload Null safety Six platforms THE ENGINEERING THE REALITY THE NEXT BET Impeller Production apps AI-native interfaces Trust, earned one problem at a time.
31. Flutter didn't win because it had no problems. It won because it kept engineering through them. Flutter won the right to be taken seriously.
32. S SA GDE ACADE MY Questions? Experiences, war stories, disagreements — all welcome. Nicholas Gidudu Yunwen Eric Flutter Developer Software Engineer · Flutter Developer