Loading Too Many Repeater Cards

In Mobile UI.
I use cards (embedded view on a repeater) instead of table.

For large dataset, the UI will show all cards in one load time (which is very slow coz of large dataset)

Are we able to implement, "Scroll Down - Show More - Refresh Query" kinda thing?

Implement your own pagination, where the query is aware of what value range to return. You can set this up to be "between X and Y", or "between 0 and X". The 0 and X route sounds more like your use case where you always want to display the first rows, and just add more on to the end as the user chooses.

The tricky part i am thinking is on, where the user wants more data, so a query is sent to get only the "more data" and the mechanism join the new dataset with the dataset already loaded..

Are you also seeing this way? Is the part data by part data join doable, programmatically?

Not through a biding, no. What you're describing is a function executed on-demand that appends some data to an existing data structure. Absolutely doable, but not as a binding.