Scenario: New posts are being made to USA group at 50 posts per minute. Currently, pagination will load "next 20" but will not function correctly at high volume.
Newsfeed loads page 1... A, B, C, D, E, F, G, H
(New Items -50, -49, -48, -47, etc. have been posted)
User scrolls down to load page 2: and system will load -50, -49, etc. as page 2 (Wrong)
Instead, user should see page 2 relevant to page 1 starting item.
User should scroll down to page 2 based on cursor position/anchor of "A" as original post, so page 2 should show, I J K L M N O
So, if implemented, then this will happen:
If user pulls to refresh or reloads feed, then page 1 will show -50, -49, -48, etc, then page 2 will show -35, -34, -33, etc... then page 3 will load. etc.
User pulls to refresh and page 1 shows -100, -99, -98, -97, etc... page 2 shows next 15/20, etc.
How long will it take to implement this on backend @igaponov ?
Scenario: New posts are being made to USA group at 50 posts per minute. Currently, pagination will load "next 20" but will not function correctly at high volume.
Newsfeed loads page 1... A, B, C, D, E, F, G, H (New Items -50, -49, -48, -47, etc. have been posted) User scrolls down to load page 2: and system will load -50, -49, etc. as page 2 (Wrong) Instead, user should see page 2 relevant to page 1 starting item. User should scroll down to page 2 based on cursor position/anchor of "A" as original post, so page 2 should show, I J K L M N O
So, if implemented, then this will happen: If user pulls to refresh or reloads feed, then page 1 will show -50, -49, -48, etc, then page 2 will show -35, -34, -33, etc... then page 3 will load. etc. User pulls to refresh and page 1 shows -100, -99, -98, -97, etc... page 2 shows next 15/20, etc.
How long will it take to implement this on backend @igaponov ?