recloudstream / recloudstream/cloudstream

Better download feedback / queue view

Open
#1,166 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement TODO
Dominant language
Kotlin
Stars
10.7k
Forks
1.1k
Avg merge
1d 23h
Merged PRs (30d)
15

Description

Describe your suggested feature

Example:
I go to a movie/ series and click on "download"

Current Behavior:

  • The button seems to get pressed, and you need to wait for a toast message to tell you if it is doing something, this can take a few seconds.
  • After that, the download icon appears, assuming the download queue is currently empty and it taking new things.
  • If you go to the downloads section, the queued but not yet started downloads will not appear, so you don't know if you even put them in queue or not
  • If any download before that fails, you will not know, and you need to search everything back up and hope that it does it right this time...

Expected Behavior:

  • When the download button is clicked, it should show something like "In Queue" or something similar
  • There should be a subsection in the downloads section where you can see the download queue
  • One should be able to modify the queue (remove and move items, etc.)
  • See failed items that were in the queue
Other details

As of now, the download feature seems to be held together with sticks and Duct Tape and fails when you look at it in the wrong way...

This issue is definetly not solely a provider issue

Currently, on pre-version: a5582a7

Acknowledgements
  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
  • I have written a short but informative title.
  • I will fill out all of the requested information in this form.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the existing download flow and the downloads section to understand how queued, active, and failed items are represented. Done should include immediate queue feedback, visible queued and failed downloads, and controls to remove or reorder queued items.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.