This message was deleted.

My first thinking is that gathering all tracks on initial load at a top-level and passing that to inner components. somehow that data needs to be updated when participants connect/disconnect and I should re-render only the relevant track. I would appreciate any pointers.

hi @freezing-school-32083 we released this library just today as a preview, there are some examples in the repo at https://github.com/livekit/components-js that should help you get started. Feel free to ask more questions if things are still unclear. We are actively working on improving the documentation for this as well.

thank you. while all examples are good for high-level use (as in developing a video conference-app), in my case (where I only need tracks to play selectively) I guess I need to use the hooks to gather the initial participant-track pairs, pass that to my app through a provider and use it on the relevant component? I am not even sure if that’s the right abstraction, just looking for ideas

yeah, that sounds about right. In case you are going to use

autoSubscribe: false

as an option: we haven’t optimized the library for this use case yet, but would be great to know your thoughts once you explored the options. For gathering tracks, it will depend on how you would like to filter them. The TrackLoop and TileLoop both take a

filter

argument, so you could get away with just using that, depending on how your selection works. other than that you are right, you would use the

useTracks

loop and get the pairs that you are interested in and render them either with

ParticipantTile

or a custom UI view