Flutterflow: SQLite Local Database Sync to Firebase and Supabase Trick Revealed! | OFFLINE/ONLINE 

Glad to be of help.

Thanks for watching!

Haha, thank you man. Glad to hear this was useful to you.

Happy to help!

Thank you for pointing out. I'm just learning about PowerSync hearing from you. The reason I used this method is to show a general means by which it can be achieved whether you are using Supabase, Firebase, or any Custom DB. The whole idea is how the structuring, and computation can be used.

Who has experience with PowerSync? And what is the experience?

You create a page state initialize it at 0, the you loop with the condition that if(page state

I considered that as basic FlutterFlow concepts. I'd recommend to check FlutterFlow docs here docs.flutterflow.io/

You are right using a boolean value should work perfectly. Now there are several reasons why using timestamps is much better. Without going into much detail, - Using a timestamp provides more granularity in tracking when a specific change occurred. - It can be useful for scenarios where the order of changes matters. - Say for some reason or a different use case multiple clients can make changes concurrently, using a timestamp allows for better conflict resolution. You can compare timestamps to determine which change should take precedence. - Timestamps can be useful in offline scenarios where changes made while offline need to be synchronized based on when they were made. Boolean may not be complex to implement like timestamps but it is important to know what you wan to make use of before choosing.

@@Nocode_Solutions omg this response is just a gold!!!!! lemme print it out and frame it so when I wake up I will read it every day and remember I gotta learn much much more! Bro your coding knowledge def on like another lvl. Hope one day to know as much as you! Thank you for this break down!

@@KaiCodingJourneyThe rabbit hole gets a whole lot deeper once you get to error handling where multiple people could be editing data concurrently 😂 This is why timestamps are vital. If three edits occur to a record (A, B & C) (in timestamp order), however B was edited offline and is synced to the database after C, and there are changes to the common fields, how are you going to deal with this? Are there automatic rules you want to apply? Often there aren’t, in which case you will need to store these versions/changes somewhere and require a user (more UI, more business logic) to review to decide which version (B, C or combination of B/C field data) should prevail…what if another user or an automated process attempts to create a version D edit before the first error has been reviewed? Are they starting from a base record of version C or B? Should you even let them create further edits to the record or do you lock it for editing? What are the implications for offline users who have subscribed (don’t get me started on managing publication/subscription approaches!) to this record/group of records and therefore have very outdated records on their device? Do you impose time limits on edits in between syncs? FlutterFlow is a great tool, but it tends to encourage people to think they can create any type of app when there are significantly different levels of architectural complexity required to do so depending upon what type of app you seek to build. Large concurrent B2B apps may see the above scenarios occur frequently (CRMs, ERPs, MRPs, HRIS systems etc) if they desire offline functionality, where as consumer (B2C) focused systems will see far less of this unless they rely on significant amounts of data sharing (concurrent editing.) If you are building an app with no sharing of data (pure B2C) then adopting this offline first approach is not only pretty simple, but it’s a real winner from a functionality and UX perspective. Take the opportunity to learn about architectural design patterns and approaches when you have some time as it will definitely help get your heard around these challenges, then it’s just a question of how you want to approach it.

@@KaiCodingJourney Sure thing man, Practice, Practice, Practice :)

@@awlhunt You are utterly correct! It can get as complex as it can be. That is why in most solutions, you only see a subset or just a very brief functionality allowing for both Online Offline functionality. Let's take for example a chat application: If I compose and send a message while offline, it notes when I did that and then... should it send the message when I get online using the time I came online? or using the time I created the message while I wasn't connected? [ A good example when boolean can't be used again]. A good knowledge on architectural design can help make the bests decisions here. Thank you @awlhunt.

I'm hoping it'll get better subsequently. Thank you