Implement pagination Logic + UI for all the data collections coming from Content Gateway

Status

Completed

Assign

Date

Priority

Normal

Type

Improvement

The current version of the app doesn’t implement any pagination mechanism, so when a list is loaded on a screen anywhere..

The user sees all the records returned by the API;

Content Gateway API returns a limited list of data - usually up to 100 items - expecting the app to use pagination API to receive more data.

In other words, Content Gateway API implements pagination, but the mobile app UI and Data layers don’t.

We need to update Content Gateway API integration and the app’s Service layer to support pagination, and update the UI so that tables and collections load data chunks dynamically and gradually.

Implement pagination Logic + UI for all the data collections coming from Content Gateway

Status

Completed

Assign

Date

Priority

Normal

Type

Improvement

The current version of the app doesn’t implement any pagination mechanism, so when a list is loaded on a screen anywhere..

The user sees all the records returned by the API;

Content Gateway API returns a limited list of data - usually up to 100 items - expecting the app to use pagination API to receive more data.

In other words, Content Gateway API implements pagination, but the mobile app UI and Data layers don’t.

We need to update Content Gateway API integration and the app’s Service layer to support pagination, and update the UI so that tables and collections load data chunks dynamically and gradually.