NXL-11071112320 Feat: Implement priority-based animator image preloading#189
Closed
Panguino wants to merge 0 commit into
Closed
NXL-11071112320 Feat: Implement priority-based animator image preloading#189Panguino wants to merge 0 commit into
Panguino wants to merge 0 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
d52e2c0 to
1671e53
Compare
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
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.
Monday.com Item
Monday Item ID: NXL-11071112320
Description
Problem: The animator component loaded ALL frames sequentially before displaying any content. Users experienced a 2-5 second delay staring at a loading panel before seeing any imagery, even though they only needed to see the current frame immediately.
Solution: Implemented priority-based image loading that loads the current frame first and displays it immediately (within ~100-300ms), then loads remaining frames in the background using a spiral pattern (next, previous, next+1, previous-1, etc.).
User Impact:
Technical Details:
Loading Pattern:
If current frame is index 5, the loading order is:
... continues spiraling outward
How Has This Been Tested?
Manual Testing Required:
Immediate Display Test:
Background Loading Test:
Animation Playback Test:
Cache Performance Test:
Multiple Sections Test:
Edge Cases Verified:
Screenshots/GIF (if appropriate):
N/A - Performance improvement, best validated through manual testing
Types of changes