I can think of several ideas for improving the frontend’s perceived responsiveness. Trakt will once again be a prominent touchstone for me; sorry, it’s been 13 years and I really think they had it right the first (well, second) time with “Trakt V2”.
Another big annoyance for me is taking several seconds to load the first time I visit WeTrakr for the day. I’ll land on a completely blank Profile page while it fetches everything.
Trakt’s V2 frontend cached a bunch of stuff in LocalStorage (which items were marked as played, ratings, collection/library status, etc.) so it was faster to load different views from the server.
They’ve shut that version down so I can’t check, but I suspect it also had some Service Worker component to make sure important scripts stayed cached and never show the user an empty page the way WeTrakr sometimes does.
dgw
•
Sep 30
Not sure if it needs a separate Idea post: Server-side rendering of the initial page view could also help with the “loads a blank page” issue. Especially noticeable on my decidedly midrange phone, which takes up to several seconds to show anything besides the header logo and footer links as it processes the app’s scripts.
i.vegaz
•
Jul 31
Currently when i go to a movie detail page from a list and come back its loading and change in scroll position. its annoying
Log in to comment and vote
Comments3
dgw
Aug 16
I can think of several ideas for improving the frontend’s perceived responsiveness. Trakt will once again be a prominent touchstone for me; sorry, it’s been 13 years and I really think they had it right the first (well, second) time with “Trakt V2”.
Another big annoyance for me is taking several seconds to load the first time I visit WeTrakr for the day. I’ll land on a completely blank Profile page while it fetches everything.
Trakt’s V2 frontend cached a bunch of stuff in LocalStorage (which items were marked as played, ratings, collection/library status, etc.) so it was faster to load different views from the server.
They’ve shut that version down so I can’t check, but I suspect it also had some Service Worker component to make sure important scripts stayed cached and never show the user an empty page the way WeTrakr sometimes does.
dgw
Sep 30
Not sure if it needs a separate Idea post: Server-side rendering of the initial page view could also help with the “loads a blank page” issue. Especially noticeable on my decidedly midrange phone, which takes up to several seconds to show anything besides the header logo and footer links as it processes the app’s scripts.
i.vegaz
Jul 31
Currently when i go to a movie detail page from a list and come back its loading and change in scroll position. its annoying