Is your feature request related to a problem? Please describe.
Currently a full app load retrieves all documents of all Firestore collections. This causes extended loading time and read actions.
Describe the solution you'd like
The two biggest collections are songs and setlists. The former is needed as a whole for creating setlists (which would be complicated to implement with lazy loading, maybe as a follow up improvement when this issue landed), but the latter could be limited to display only setlists of the previous year or previous 6 months. This would reduce the payload heavily.
Older setlists could be loaded on demand, e.g. when searching or navigating for setlists.
Describe alternatives you've considered
None.
Additional context
In itself it is not so bad to load all setlists/collections, but long term this could cause issues with reading actions quota.
Is your feature request related to a problem? Please describe.
Currently a full app load retrieves all documents of all Firestore collections. This causes extended loading time and read actions.
Describe the solution you'd like
The two biggest collections are
songsandsetlists. The former is needed as a whole for creating setlists (which would be complicated to implement with lazy loading, maybe as a follow up improvement when this issue landed), but the latter could be limited to display only setlists of the previous year or previous 6 months. This would reduce the payload heavily.Older setlists could be loaded on demand, e.g. when searching or navigating for setlists.
Describe alternatives you've considered
None.
Additional context
In itself it is not so bad to load all setlists/collections, but long term this could cause issues with reading actions quota.