Hey there,
I've been diving into Flutterflow while working on a desktop app, and I'm intrigued by the potential of creating a custom data type like "invoices" and storing it within an app status for local usage. As I navigate this aspect, a couple of questions have arisen, and I'd love to tap into the community's expertise to gain a better understanding.
Firstly, I'm curious about the mechanics underlying Flutterflow's handling of data persistence in such cases. When I create a custom data type like "invoices" and store it in an app status for local usage, is this data stored as a variable in memory, or does Flutterflow leverage an SQLite file, or perhaps it employs a different methodology altogether? The key objective here is to ensure that my data remains exclusively stored locally within the desktop app.
Furthermore, as I delve into this realm of local data storage, I'm also interested in understanding the capacity of data records that Flutterflow can effectively manage. In other words, is there a limit to the number of data records that can be stored and managed through Flutterflow's local storage mechanisms?
If anyone in the community possesses insights into the inner workings of Flutterflow's local data storage mechanisms and can shed light on the potential limitations regarding data records, I would greatly appreciate your input. Your knowledge and experience would not only benefit me but also fellow developers who are navigating similar terrain.
Looking forward to engaging in insightful discussions and expanding our understanding together!
