Hello, I've got couple of questions about query caching. Basically, I'm trying to understand how query caching works for per session.
1- FlutterFlow is kind of limited when it comes to caching feed page in a social media app since you can't enable pagination and cache at the same time. Feed page should be stored in session, in other words should reset when app is closed. So I think using a service like Redis or Hive is unnecessary here. So my first question is does using app state for this make sense? I guess documents/rows should first be converted to json and then stored in app state after querying. If this is valid then how much data can app state actually store?
2- Another scenario is when trying to view somebody's profile. I'd also like to store profile details of users so if they come back to that one specific profile, I won't make the same query. Query caching can be used here but now if that user makes any changes like uploading a post then their stored information won't be up to date. And I think "Clear Query Cache" option can't be used since it will be based on another user's actions or maybe I'm missing something here. Or caching user's profiles doesn't make any sense at all?
3- My last question is, what are the differences between querying a collection from inside FlutterFlow and making an api call in terms of performance or security?
Please let me know if there are better alternative ways, thanks.