Thumbnails seem to download all at once, consider prioritizing load sequence from top to bottom. #106
Labels
No labels
android: closed alpha
android: open beta
app-parity
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
creator
Epic
good first issue
hacktoberfest
help wanted
icebox
Invalid
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
product review
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-android#106
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Issue
Steps to reproduce
Expected behaviour
The thumbnails should likely try to prioritize which ones load first so that I'm not waiting for all of them to load even if I don't scroll down very far.
Actual behaviour
Tell us what happens instead
Anything Else
Google aims to have the search result that you're going to see as the top result and tries to improve if it doesn't get you to click the top link based on your search result.
Google Chrome also attempts to load as much of the website as possible before showing you any updates on the user interface which gives the impression that the website loads faster. Users tend to be more frustrated having to wait for elements to load bit by bit. It would be marginally better to show a loading element instead.
A non-trivial issue, UX specific, Improvement.
Thanks for submitting this issue!
This is a known issue in the LBRY-app as well and the root cause is a very slow client/server connection for the wallet server. The wallet server is responsible for "resolving" each URL in order to get the thumbnail and other metadata. Currently, we batch these requests all into one so not to overload the server with hundreds of requests.
The wallet client/server re-worked mentioned in the latest development update should speed up this process, and if not, we can think of better ways to batch them so they show up quicker.
@tzarebczan are there relevant links that could be dumped into this issue to make the job easier in the future?
This experience should be much improved on the latest app version. Going to close this for now, but if anyone runs into something similar, please reopen.
Thanks @tzarebczan this was solved shortly after I posted it, within a week or so I believe unfortunately I'd not closed the ticket.