Thumbnails seem to download all at once, consider prioritizing load sequence from top to bottom. #106

Closed
opened 2018-05-06 21:28:18 +02:00 by Leopere · 4 comments
Leopere commented 2018-05-06 21:28:18 +02:00 (Migrated from github.com)

The Issue

Steps to reproduce

  1. Launch the app
  2. Wait for media to load on Dashboard
  3. Patience

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 reporting an issue to LBRY and helping us improve! To make it possible for us to help you, please fill out below information carefully. Before reporting any issues, please make sure that you're using the latest version. We are also available on live chat at https://chat.lbry.io --> ## The Issue ### Steps to reproduce 1. Launch the app 2. Wait for media to load on Dashboard 3. Patience ### 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.
tzarebczan commented 2018-05-07 18:32:51 +02:00 (Migrated from github.com)

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.

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.
Leopere commented 2018-05-10 06:17:14 +02:00 (Migrated from github.com)

@tzarebczan are there relevant links that could be dumped into this issue to make the job easier in the future?

@tzarebczan are there relevant links that could be dumped into this issue to make the job easier in the future?
tzarebczan commented 2018-09-14 20:10:42 +02:00 (Migrated from github.com)

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.

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.
Leopere commented 2018-09-15 21:07:24 +02:00 (Migrated from github.com)

Thanks @tzarebczan this was solved shortly after I posted it, within a week or so I believe unfortunately I'd not closed the ticket.

Thanks @tzarebczan this was solved shortly after I posted it, within a week or so I believe unfortunately I'd not closed the ticket.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-android#106
No description provided.