10/05/2026
I attended Flutter Guild 2026 at Brain Station 23
Industryâāϰ āĻāĻŋāĻā§ brilliant developer āĻĻā§āϰ āϏāĻžāĻĨā§ meet āĻāϰāĻž, ideas exchange āĻāϰāĻž, āĻāϰ real engineering discussion āĻĨā§āĻā§ āĻļā§āĻāĻžāϰ experienceāĻāĻž āϏāϤā§āϝāĻŋāĻ āĻ
āύā§āĻ āĻāĻžāϞ⧠āĻāĻŋāϞāĨ¤
āϏāĻŦāĻā§ā§ā§ āĻŦā§āĻļāĻŋ āĻāĻžāϞ⧠āϞā§āĻā§āĻā§ āĻĒā§āϰāĻĨāĻŽ āĻĻā§āĻāĻāĻž sessionāĨ¤ āĻāĻŋāĻā§ notes & takeaways āĻļā§ā§āĻžāϰ āĻāϰāĻāĻŋ â
đ Session 1 â Why Flutter apps feel slow and how to actually find it?
Speaker: Momshad Dinury Bhai
âĸ Flutter performance āĻ
āύā§āĻāĻāĻžāĻ depend āĻāϰ⧠rendering pipeline āĻŦā§āĻāĻžāϰ āĻāĻĒāϰ
âĸ 60 FPS āĻŽāĻžāύ⧠āĻĒā§āϰāϤāĻŋ frame āĻāϰ āĻāύā§āϝ āĻĒā§āϰāĻžā§ 16.7ms budget āĻĨāĻžāĻā§, āĻāĻŦāĻ smooth rendering āĻāϰ āĻāύā§āϝ UI & Raster āĻāĻžāĻāĻā§āϞ⧠āĻāĻ time budget āĻāϰ āĻŽāϧā§āϝ⧠finish āĻšāϤ⧠āĻšā§
âĸ UI Thread â Raster Thread â GPU flow āĻŦā§āĻāϤ⧠āĻĒāĻžāϰāϞ⧠bottleneck identify āĻāϰāĻž āĻ
āύā§āĻ easier āĻšā§
âĸ Different device (RAM, CPU, GPU) āĻ
āύā§āϝāĻžā§ā§ real-world performance behavior āĻ
āύā§āĻ change āĻšāϤ⧠āĻĒāĻžāϰā§
âĸ Flutter DevTools āĻĻāĻŋā§ā§ frame jank, dropped frames, navigation related slowdown āϏāĻšāĻā§ identify āĻāϰāĻž āϝāĻžā§
âĸ Proper image caching rendering performance āĻ
āύā§āĻ improve āĻāϰāϤ⧠āĻĒāĻžāϰā§
âĸ āĻ
āύā§āĻ performance issue āĻāϏ⧠āĻā§āĻ āĻā§āĻ decision āĻĨā§āĻā§:
- SingleChildScrollView āĻŦā§āϝāĻŦāĻšāĻžāϰ āĻāϰāĻž āϝā§āĻāĻžāύ⧠ListView.builder āĻŦā§āĻļāĻŋ appropriate
- build() method āĻāϰ āĻāĻŋāϤāϰ⧠heavy operation āϰāĻžāĻāĻž
- improper image caching
âĸ āϏāĻŦāĻā§ā§ā§ āĻāĻžāϞ⧠āϞā§āĻā§āĻā§ â session āĻāĻž theory āĻāĻŽ, practical problem finding āύāĻŋā§ā§ āĻŦā§āĻļāĻŋ focused āĻāĻŋāϞ (âhow to actually find the problemâ)
đ Session 2 â Building with Agentic AI
Speaker: Utpal Barman Bhai
âĸ AI development fast āĻāϰ⧠āĻĻāĻŋāĻā§āĻā§, but validation harder āĻšā§ā§ āϝāĻžāĻā§āĻā§
âĸ Coding easier āĻšāĻā§āĻā§, āĻāĻŋāύā§āϤ⧠architecture & decision-making āĻāϰāĻ important āĻšā§ā§ āĻāĻ āĻā§
âĸ Architect vs Executor mindset āĻāĻž āĻ
āύā§āĻ insightful āĻāĻŋāϞ
âĸ AI āĻā§ proper context āĻĻā§ā§āĻž āĻā§āĻŦ important:
- project-level understanding
- memory/context
- reusable skills
- clear rules (do & donât)
âĸ Important habit:
AI āĻā§ blindly accept āύāĻž āĻāϰ⧠âWhy this?â āĻāĻŋāĻā§āĻā§āϏ āĻāϰāĻž
đ Panel Discussion āĻĨā§āĻā§ āĻāĻŋāĻā§ valuable point:
âĸ Communication skill improve āĻāϰāĻž
âĸ āĻļā§āϧ⧠framework āĻāϰ āĻŽāϧā§āϝ⧠limited āύāĻž āĻĨāĻžāĻāĻž
âĸ Concepts deep dive āĻāϰ⧠āĻļā§āĻāĻž
âĸ Solution build āĻāϰāĻžāϰ āĻāĻā§ business domain āĻŦā§āĻāĻž
âĸ Implementation āĻ jump āĻāϰāĻžāϰ āĻāĻā§ problem properly understand āĻāϰāĻž
âĸ āĻļā§āϧ⧠coding āύāĻž, thinking ability improve āĻāϰāĻž
âĸ āĻŽāĻžāĻāĻĒāĻĨā§ project abandon āύāĻž āĻāϰ⧠finish āĻāϰāĻž
âĸ Business āĻāĻŋāĻāĻžāĻŦā§ work āĻāϰ⧠āϏā§āĻāĻž āĻļā§āĻāĻž
âĸ Mistakes normal â important āĻšāϞ⧠āϏā§āĻāĻžāύ āĻĨā§āĻā§ āĻļā§āĻāĻž
âĸ AI era āϤ⧠adaptability & soft skills āĻ
āύā§āĻ important āĻšā§ā§ āϝāĻžāĻā§āĻā§
Overall, event āĻāĻž āĻāĻŦāĻžāϰ remind āĻāϰāĻŋā§ā§ āĻĻāĻŋāϞ â
Good engineering āĻļā§āϧ⧠code āϞā§āĻāĻž āύāĻžāĨ¤
āĻŦāϰāĻ problem āĻŦā§āĻāĻž, thoughtful decision āύā§ā§āĻž, āĻāϰ continuously āĻļā§āĻāĻžāϰ āύāĻžāĻŽāĻ engineeringāĨ¤
Send a message to learn more