So i moved from creating apps on google appsheet and then glideapps and both have realtime by default for anything going on in the apps created on them, hence my amateur question. I'm now exploring weweb/flutterflow with supabase. So if i don't use realtime then how is the app updated for other users when a user updates something ? (apart from them pressing refresh or going back and forth on the page) Also if realtime is not enabled then does ateast the user who made the change see it in realtime on their app or does that also happen only on manual refresh ?
So lets say the app is a sales CRM. Their a hierachy of roles. A sales agent punches in the sales. Their manager, Accountant and the director of the company should be able to see that immediately because manager needs to be updated immediately if any changes are to be made, accountant needs to make some verifications/entry based on this and the director has an analytics dashboard which if not in realtime won't change unless refreshed. Same would go for an inventory app or a task management app or a production monitoring app. None of these are chat apps but the work being done via these apps is to be made immedietly available to certain users(not all but realtime is not as per user i think). So back to my question : Are there any tradeoffs in terms of cost/performance if i have realtime enabled for all tables ?
<@869319595784290395> got it. Thanks
My question is that as devs can we continue to rely on supabase as our goto BaaS (although its not their fault maybe) for creating client apps or is this like a one off situation not warranting such extreme measures ? Also what are some alternatives in that case ?