recloudstream / recloudstream/cloudstream

Smart library management features

Open
#2,204 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Describe your suggested feature

Hi devs, I'm requesting a few library-management features:

When I finish watching any content, it should automatically move from Watching to Watched.

When I start watching something from Plan to Watch, it should move to Watching.

If I stop watching any content for more than 3 months, it should automatically move to Dropped.

Also, when I reopen content that I’ve already finished, the play button should show Play Again instead of Play Movie, as if I’m watching it for the first time

Other details

Hi devs, I'm requesting a few library-management features:

When I finish watching any content, it should automatically move from Watching to Watched.

When I start watching something from Plan to Watch, it should move to Watching.

If I stop watching any content for more than 3 months, it should automatically move to Dropped.

Also, when I reopen content that I’ve already finished, the play button should show Play Again instead of Play Movie, as if I’m watching it for the first time

Acknowledgements
  • My suggestion is NOT about adding a new provider
  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.

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 library status transitions and the playback button entry point used for movie or episode content. Define how completion, starting planned content, three months of inactivity, and replaying finished content should be detected, then verify each transition and the resulting button label across the relevant screens.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, 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.