Open brocollie08 opened 1 year ago
@brocollie08, I posted on issue #90, I'd like to get involved in this project. I see this is "good first issue". Does this issue need to be predecessor to #90 ?
@OleDakotaJoe Thanks for your interest in contributing!
This one is not necessarily a pre-req for #90 but you won't be able to easily see the outcome of #90 without this.
I edited the original description with some more code, you can see in the case of ManagedPlayerState.Running
, asset.compose()
is called, that's where the connection is between these two issues, that's the entry point for the asset being rendered on the UI
Give the consumers a way to render Android Player rendered UI as a
@Composable
so they are able to choose between renderingComposable
Player assets and traditional Android view Player assetsWe currently have working code for a composable Android
ManagedPlayer
(multi-flow experiences) as followsThis code has not been moved into this project, we would like to potentially patternize it and move it over, as well as creating a similar composable for a single flow experience by feeding in an
AsyncFlowIterator
with one flow