Infinite scrolling is a software design technique that loads content continuously as the user scrolls down the page/screen.
Pros | Cons |
---|---|
It works offline and is low-latency (data loads quickly from the local database). We don’t need to load data from the backend via the network when the user reaches the bottom of the page/feed/list. | There will be cases where this approach won’t work because the total volume of data might become too large for the local database - for example, when there’s a wide range of tables that the user needs to be able to infinite scroll. Your app allows the user to apply filters to the displayed data, which results in fewer pages displayed from a large dataset, and therefore limited scrolling. |
Pros | Cons |
---|---|
Does not require updating flags in your backend database. Enables client-side control over what data is synced. | We can only sync additional data when the user is online. There will be latency while the user waits for the additional data to sync. |
Pros | Cons |
---|---|
This requires syncing less data to each user, which will result in a faster initial sync time. | We can only load additional data when the user is online. There will be some latency to load the additional data (similar to a cloud-first app making API calls). In your app code, records loaded from the API will have to be treated differently from the records loaded from the local SQLite database. |
Pros | Cons |
---|---|
This requires syncing less data to each user, which will result in a faster initial sync time. | We can only perform the trigger and sync additional data when the user is online. There will be higher latency: Both for the API call to update the flags, and for syncing the additional data. We do not necessarily recommend going this route: There’s higher latency and it’s not a particularly elegant architecture. |