Skip to content
This repository has been archived by the owner on Dec 1, 2020. It is now read-only.

Investigate switching from react-native-web to react-native-dom. #6

Open
EraYaN opened this issue Apr 6, 2019 · 3 comments
Open

Investigate switching from react-native-web to react-native-dom. #6

EraYaN opened this issue Apr 6, 2019 · 3 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@EraYaN
Copy link
Contributor

EraYaN commented Apr 6, 2019

This would allow us to use https://github.com/react-native-community/react-native-video, but I feel it might be quite involved to switch.

@EraYaN EraYaN added enhancement New feature or request help wanted Extra attention is needed labels Apr 6, 2019
@EraYaN EraYaN added this to the Video Playback milestone Apr 6, 2019
@anthonylavado
Copy link
Member

Whoa that looks really good, including a method to get playback progress... that would solve some issues for Android using exoplayer as it is
Cc @thornbill

@EraYaN
Copy link
Contributor Author

EraYaN commented Apr 6, 2019

ExoPlayer will also make sure all HDR and audio formats are properly passed through for Android TV devices.

@mark-monteiro
Copy link

I did some research on react-native-dom because I'm always interested in trying to keep up with the react ecosystem :)

The project sounds neat, but as of now development appears to be halted and more likely the project is dead entirely: vincentriemer/react-native-dom#102 (comment).

The react-native-video component may still be a good solution, in combination with some sort of platform-specific exception for web.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request help wanted Extra attention is needed
Development

No branches or pull requests

3 participants