You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a general issue to highlight we're currently working towards a Beta release of the library. You'll find all related issues in our Beta project board.
Goals
The primary goal moving into Beta is to open the player up to the public so we can start gathering feedback on the road to 1.0. We're still stress testing this player in a variety of ways at Reddit, but we need more diversity in feedback, especially around the UI building/customization.
Related to this primary goal are the following:
A stable player foundation/architecture.
A stable foundation for player UI building and styling.
Comprehensive documentation and examples.
Stable here simply means no more breaking changes.
Non-Goals
Reaching feature parity with Vime/Plyr. This means that not all providers and player functionality will be available in Beta. This goal is planned for our 1.0 release which should sharply follow the Beta release. Why? Simply because we feel it's more important to get the player into more hands at this early stage, so we can gather feedback before we move forward. To note, we might still build some features out during Beta in-parallel with 1.0 if time permits.
You can find them here, but the list might be deceiving as more functionality than what's visible at the surface is or will be possible. We'll provide more information on that soon.
❓ Will any framework integration wrappers be available?
The only one that is planned for the Beta release is React, since other frameworks now completely support web components. The React integration will also be our opportunity to test out SSR options.
Other integration wrappers such as Svelte/Vue are definitely still being considered for both SSR and better DX reasons.
Comments
If you have any concerns/questions/requests for this Beta release, please let us know below👇 It's important to note that having solid reasons, accompanied with potential business use-cases and examples for why something should be prioritized, is going to go much further than suggesting you simply want something.
The text was updated successfully, but these errors were encountered:
We're so close to releasing the Player Beta! We're just documenting some of the elements you'll be using from the library before announcing it. Few interruptions slowed us down, but we're on track for this week.
It's Beta time -> #626.
This is a general issue to highlight we're currently working towards a Beta release of the library. You'll find all related issues in our Beta project board.
Goals
The primary goal moving into Beta is to open the player up to the public so we can start gathering feedback on the road to 1.0. We're still stress testing this player in a variety of ways at Reddit, but we need more diversity in feedback, especially around the UI building/customization.
Related to this primary goal are the following:
Stable here simply means no more breaking changes.
Non-Goals
Reaching feature parity with Vime/Plyr. This means that not all providers and player functionality will be available in Beta. This goal is planned for our 1.0 release which should sharply follow the Beta release. Why? Simply because we feel it's more important to get the player into more hands at this early stage, so we can gather feedback before we move forward. To note, we might still build some features out during Beta in-parallel with 1.0 if time permits.
FAQ
❓ Which providers will be supported in the Beta?
hls.js
)❓ What functionality will be available?
We currently support the entire native HTMLMediaElement spec which includes everything like
autoplay
,playsinline
,paused
,muted
,volume
, etc.You can find all currently supported properties here, and events here.
❓ What UI components are available?
You can find them here, but the list might be deceiving as more functionality than what's visible at the surface is or will be possible. We'll provide more information on that soon.
❓ Will any framework integration wrappers be available?
The only one that is planned for the Beta release is React, since other frameworks now completely support web components. The React integration will also be our opportunity to test out SSR options.
Other integration wrappers such as Svelte/Vue are definitely still being considered for both SSR and better DX reasons.
Comments
If you have any concerns/questions/requests for this Beta release, please let us know below👇 It's important to note that having solid reasons, accompanied with potential business use-cases and examples for why something should be prioritized, is going to go much further than suggesting you simply want something.
The text was updated successfully, but these errors were encountered: