I want to build in a Meet component on a page and I also want some room presense / y.js / etc stuff on that page. It would be nice to re-use existing webrtc capability instead of adding a second mechanism for basically the same thing.
Livekit has it, BUT it uses Livekit’s rooms and participants to be created by Livekit’s SDKs.
By any chance, are Meet’s rooms/participants and Livekit’s rooms/participants essentially the same thing in the same DB? E.g. if I create a room via Livekit server SDK, would I be able to just straight away point Meet to that room’s URL?
Hi @Kazimir_Podolski ,
Thanks for the clarification and for outlining your use case.
If you create a room via the LiveKit Server SDK, you would not be able to simply point Meet to that room. OpenVidu Meet creates and manages its own rooms, and those are associated with LiveKit rooms internally — not the other way around. So rooms created directly through LiveKit are not automatically compatible with Meet.
Regarding reusing the existing WebRTC capability (e.g., for messaging instead of introducing a second real-time mechanism), this is something we do have on our roadmap. Improving how WebRTC can be leveraged beyond audio/video is an area we’re planning to address.
To better understand your needs and make sure we’re building the right thing, could you share:
- What specific functionality you’re looking to implement?
- How you’d like to use it alongside the Meet component?
- What outcome you’re trying to achieve, or what problem this would solve for you?
This context would help us evaluate the best approach and prioritize accordingly.
OpenVidMeet creates and manages its own rooms, and those are associated with LiveKit rooms internally — not the other way around. So rooms created directly through LiveKit are not automatically compatible with Meet.
Interesting, so rooms created via Meet REST API should actually be visible to Livekit SDK? Does the association work simply by having the same roomId in Meet in Livekit? Then I can just manage rooms via Meet and use Livekit SDK for the rest. It would mean partial compatibility which should be enough e.g. for Data purposes as it only uses a room, not creates one.
And what about participants then?
Yes. Once a Meet Room has been created and becomes active—meaning at least one participant has joined—the LiveKit SDK is able to detect and interact with it.
Yes. The roomId of a Meet Room is directly mapped to the LiveKit roomName, maintaining a one-to-one association between both identifiers.
You can currently send data messages to the room using the LiveKit SDK. However, on the Meet side, those messages will have no effect unless there is an explicit listener implemented to handle them (which it is not supported now).
Could you provide more details about your intended flow or use case?
Same for participants, you can access to them through LiveKit SDK.
1 Like
Perfect, I think it should do for us then.
We’re working on an online tutoring platform and basically we have a page with online collaboration between users during the meeting. We’re trying to use Meet component on the page with the rest of collaborative work managed by us.
Chances are Meet would be too restrictive and we’ll need to re-invent our own meeting UI, but for now we’re trying to re-use as much as possible.
Our goal is to offer a product that is as flexible and customizable as possible so it can integrate smoothly into a wide variety of client use cases, including platforms like yours where collaboration features extend beyond the meeting itself.
We understand that in some scenarios the current Meet UI may be a little more flexible than now it is, especially when you need tight control over the overall user experience. Expanding customization capabilities and integration flexibility is part of our roadmap, including enabling deeper embedding and UI control options similar to what we’ve been discussing.