Hi everyone, I'm building a grocery app for a client and wanted to get some feedback on my architecture and tech stack choices.
Stack:
Frontend: Flutter (State management: Provider)
Backend: Supabase (Auth, PostgreSQL, Realtime for order tracking)
Payments: Razorpay
Key Features: Real-time stock updates, role-based access (Customer/Admin/Delivery), and order history.
My Questions:
Is Provider sufficient for a complex cart system with multiple discount logic, or should I consider moving to Riverpod for better dependency injection?
What are the best practices for handling Supabase RLS for a multi-role app (Customer vs. Delivery)?
Has anyone experienced performance issues with Supabase's Realtime when handling many simultaneous users in a high-traffic grocery scenario?
Any feedback or "wish-I-knew-this" tips would be greatly appreciated.
The user is seeking feedback on their tech stack for a grocery app using Flutter, Supabase, and Provider. They inquire about the adequacy of Provider for complex cart systems, best practices for Supabase RLS in multi-role apps, and performance issues with Supabase Realtime in high-traffic scenarios. They welcome any additional tips or feedback.
I made a grocery app with Flutter, Supasbase and Riverpod it's opensource: https://github.com/Cunibon/recipath
So apart from provider (which should work just fine) I can speak from experience that it works ^^
Thanks
I suggest the flutter bloc shopping cart app https://medium.com/@ThinkodeAI/flutter-bloc-shopping-cart-app-part-1-436eeb56e57f