recloudstream / recloudstream/cloudstream
Extension resource management
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 10.7k
- Forks
- 1.1k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 15
Description
Need
Recently, people have been facing many issues with CloudStream and the situation has improved a lot thanks to the recent update.
The instability seems to be caused to a great extent because of users installing a huge chunk of extensions they don't even use.
The requested feature will also improve the overall experience of users
Feature
Extension loading on demand
Profile
- The extensions will be loaded or unloaded based on the profile that uses the extensions
- Commonly used extensions will be loaded on the profile section screen itself
- This data will auto-delete every 2-3 months
Continue watching
Only the extensions used for the continue watching in the profile will be loaded
Archiving extensions
If an extension is not used for quite some time, it will automatically be uninstalled and then installed again on demand
Use case
We get most of the content we want from 1-2 extensions that we regularly use, sometimes we don't find it and use the backup extensions which keep on loading on each start-up even though we don't need them
[!NOTE]
All of the needs and use cases are from real-life user experiences and are not made up
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or entry points. Start by locating the profile, continue-watching, and extension lifecycle code, then determine how usage data, on-demand loading, and automatic archiving should fit together; done would require implementing and validating the requested resource-management behavior.
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
- Needs clarification
- Newbie friendliness
- 25/100