feat(ios): paginate older turns with infinite scroll - #347
Merged
Merged
Conversation
0xSero
force-pushed
the
rebranch/resume-existing-sessions
branch
from
September 13, 2026 18:29
d7d9b1b to
47a9813
Compare
0xSero
force-pushed
the
revive/ios-conversation-scroll
branch
from
September 13, 2026 18:29
7b9cba1 to
fc80c0a
Compare
0xSero
force-pushed
the
rebranch/resume-existing-sessions
branch
from
September 13, 2026 20:53
47a9813 to
7940f23
Compare
0xSero
force-pushed
the
revive/ios-conversation-scroll
branch
from
September 13, 2026 20:53
fc80c0a to
2082a45
Compare
0xSero
changed the base branch from
rebranch/resume-existing-sessions
to
main
September 13, 2026 20:53
Replace the explicit Load-earlier-messages button with scroll-triggered pagination. Track visible turn IDs and prefetch the next older page as the user approaches the top, debounced per cursor so concurrent prefetches collapse. Bump page size to 20, make loadOlderTurns report whether a page was actually loaded, and re-route the Latest button through a semantic ScrollPosition with a UIKit scroll-view resolver so the jump executes even while momentum is decelerating. Anchor merged exploration rows to their newest constituent turn so prepending older pages keeps scroll identity stable, and auto-collapse large conversations past a 200-item threshold.
0xSero
force-pushed
the
revive/ios-conversation-scroll
branch
from
September 13, 2026 20:55
2082a45 to
c80c723
Compare
This was referenced Sep 13, 2026
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Revival of DatScreamer's closed #308 (branch deleted), reworked onto the stacked scroll rework (#339, kingbootoshi's ScrollPosition rebuild). Fixes the iOS half of #306.
Graft strategy: the original #308 and #326 are parallel ScrollPosition-based scroll-follow redesigns. This rebranch keeps the stacked #326 scroll-follow infrastructure (edge-anchored
ScrollPosition,onScrollPhaseChangefollow state, geometry-driven follow) and grafts only the pagination features:onScrollTargetVisibilityChange+ConversationInfiniteScrollPolicy(no more "Load earlier" button)requestedOlderTurnsCursor/showOlderPageLoader)onLoadOlderTurnsnow reports whether a page loaded (asyncBool)ConversationTurnCollapsePolicyinTranscriptTurn.swift)ScrollPosition/native-scroll-view resolver/momentum jump) was dropped in favor of the stacked refactor(ios): rebuild transcript scroll follow on ScrollPosition (-159 lines) #326 implementationVerification
swiftc -parseclean on all touched filesPerformanceHelpersTests(+98 lines) run in the iOS test lane