Jump to content

Improved usability/reliability on poor connections


rechigo
Go to solution Solved by rechigo,

Recommended Posts

rechigo

After using Emby on the go, I found a few things that could be done to help improve the speed/reliability on slow mobile connections. I'm pretty tired as of writing this but I'll try to explain as best as possible.

 

1) One thing that I noticed that Emby could improve on is cancelling unnecessary HTTP requests that can severely block client operation on slow connections. An example of this is: User fires up the mobile/web app on a slow connection -> navigates over to their music library -> switches over to the playlist tab -> selects their playlist and hits play, expecting it to play within a few seconds. What happens is before the user actually switches to the playlists tab, the default tab (in this case, the suggestions tab) begins to load and continues to load even after they switch over to the playlists tab. This ends up severely blocking basically any client operation when running on a congested cell network for for instance. After applying some network presets under my devtools and testing under the same circumstances with Plex, I noticed what I originally thought they did: if I switch tabs while images/etc are still loading, the requests made to the images on the previous tab are cancelled, which noticeably increases the overall snappiness of the app. tldr; if a page is still loading and a user switches the page, cancel all requests on that page. (I hope this makes sense)

 

2) A second thing that could be done would be to implement lazy loading of images. Currently, Emby doesn't do anything for lazy loading images; it simply loads all images on a page at the same time. This isn't a big deal on any half-decent network, but put yourself in a scenario on a congested cell network and you see how it starts to block client operation.

Edited by rechigo
Link to comment
Share on other sites

 

 

What happens is before the user actually switches to the playlists tab, the default tab (in this case, the suggestions tab) begins to load and continues to load even after they switch over to the playlists tab. 

Hi there, what makes you think this? Can you give an example?

 

 

 

 

2) A second thing that could be done would be to implement lazy loading of images.

Hi there, we already have lazy loading. Why do you feel that we don't? Can you give an example?

Link to comment
Share on other sites

rechigo

 

 

Hi there, we already have lazy loading. Why do you feel that we don't? Can you give an example?

OK, after testing it appears that images do lazy load on the web app, but they do not lazy load on the android app (possibly iOS as well, but I can't test that)

 

I also noticed that the android app doesn't keep anything cached when you completely close and reopen the app, while the web app automatically stores images in disk cache. Should this thread be moved to the android section?

 

 

 

 

Sent from my SM-G973U using Tapatalk

Link to comment
Share on other sites

Android and iOS both have lazy loading as well, however it's possible the OS may clear their cached data more frequently.

Link to comment
Share on other sites

  • 1 month later...
  • Solution
rechigo

The recent updates (virtual scrolling, better lazy loading, fixed music transcoding) seem to have resolved most of this, feels about the same speed-wise as Plex does on the go. Thanks!

  • Like 2
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...