top of page
Premnath S

Premnath S

Lead Software Engineer @ ZOHO Corporation

I’m Premnath S, a Lead Software Engineer (Flutter) at Zoho Corporation with 5+ years of experience in building enterprise-grade mobile apps. Currently working on Zoho Tables — a spreadsheet-database hybrid built using Flutter. I started my Flutter journey back in college building small apps, and today I work on full-scale production products. Passionate about creating interactive, reliable UI experiences and helping developers build better Flutter apps by sharing practical insights. When I’m not coding, I’m chasing lights, shadows, and moments

Flutter State Smackdown: Comparing BLoC, Provider, Riverpod, and When to Use Them

State management is one of the most critical decisions in any Flutter app. With multiple approaches available—BLoC, Provider, Riverpod, and more—it can be overwhelming to decide which one to use, when, and why. In this talk, I will compare the most popular state management techniques, highlighting their strengths, weaknesses, and real-world use cases. Through live examples and practical demonstrations, you’ll see how each approach works in action and learn which pattern fits different types of Flutter apps, from small interactive apps to large enterprise-level products. By the end of this session, participants will understand how to choose the right state management approach, avoid common pitfalls, and apply these patterns effectively in their projects. Key Takeaways: 1.Understand the core principles of BLoC, Provider, and Riverpod, including their architecture, workflow, and lifecycle management. 2.Learn the strengths and limitations of each state management solution, with real-world examples from production apps. 3.See live demonstrations showing how to implement each pattern for common app scenarios (UI updates, API calls, and user interactions). 4.Gain practical guidance on when to choose BLoC, Provider, or Riverpod, depending on app complexity, team size, and maintainability needs. 5.Tips for avoiding common pitfalls, like unnecessary rebuilds, poor state separation, and performance bottlenecks.
bottom of page