Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Add cache path as a BetterPlayerCacheConfiguration parameter #1344

Open
A-Ghattas opened this issue Oct 26, 2024 · 0 comments
Open
Assignees
Labels
enhancement New feature or request new issue New issue which has not been checked yet

Comments

@A-Ghattas
Copy link

Is your feature request related to a problem? Please describe.
I have a use case where the app users do not have cheap access to internet, so it's crucial to have the video persist unless the user delete the app or specifically delete the cache files. The best solution I found to keep the "streaming UX" instead of downloading the videos then watch them is to change the path to somewhere outside of the temporary folder as proposed in this stackoverflow thread:
https://stackoverflow.com/questions/42273350/any-option-to-restrict-our-android-application-cache-being-cleared

Describe the solution you'd like
I want an attribute path added to the BetterPlayerCacheConfiguration

Describe alternatives you've considered
If anyone have an alternative solution to my initial problem, keeping the video persistent on the device. Please let me know.
For now, the only alternative I have is to download the videos and then play them in betterplayer from the local file, that will change the UX and my client refuses that.

Additional context
Nothing else, Thank you.

@A-Ghattas A-Ghattas added enhancement New feature or request new issue New issue which has not been checked yet labels Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request new issue New issue which has not been checked yet
Projects
None yet
Development

No branches or pull requests

2 participants