[GH-ISSUE #316] Cache playlist to avoid interface loading time #225

New issue

Open

opened 2026-02-28 14:31:29 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 14:31:29 +03:00

Owner

Originally created by @gagarine on GitHub (Jul 16, 2022).
Original GitHub issue: https://github.com/jpochyla/psst/issues/316

When you click on a playlist, you have to wait about 1s for the interface to load while psst do a network request. This is not the case with "Albums" for example.

I think playlist could be cached (and perhaps all fetched in the background at launch). When you click tracks list could then be instantly display. The network request can be done in the background once you opened a playlist and only if the playlist changed, then the interface could be updated.

This would give a

Originally created by @gagarine on GitHub (Jul 16, 2022). Original GitHub issue: https://github.com/jpochyla/psst/issues/316 When you click on a playlist, you have to wait about 1s for the interface to load while psst do a network request. This is not the case with "Albums" for example. I think playlist could be cached (and perhaps all fetched in the background at launch). When you click tracks list could then be instantly display. The network request can be done in the background once you opened a playlist and only if the playlist changed, then the interface could be updated. This would give a

kerem added the

enhancement

label

2026-02-28 14:31:29 +03:00

kerem commented

2026-02-28 14:31:30 +03:00

Author

Owner

@jacksongoode commented on GitHub (Aug 17, 2022):

This is a nice idea, how would you imagine the playlist gets updated? Just a hard refresh of the view once the request for the playlist is complete?

@jacksongoode commented on GitHub (Aug 17, 2022): This is a nice idea, how would you imagine the playlist gets updated? Just a hard refresh of the view once the request for the playlist is complete?

kerem commented

2026-02-28 14:31:30 +03:00

Author

Owner

@gagarine commented on GitHub (Aug 18, 2022):

Yes. Hard refresh is certainly fine. One things would be to keep the selected track if the user had the time to select one before the hard refresh happens.

@gagarine commented on GitHub (Aug 18, 2022): Yes. Hard refresh is certainly fine. One things would be to keep the selected track if the user had the time to select one before the hard refresh happens.