I see that Jam also offer an SDK, as a basic third party library... https://gitlab.com/jam-systems/jam/-/tree/master/ui/packages/jam-core

Something like that may save a lot of heavy lifting, and could significantly reduce the overall development time, in terms of of a re-write, but I take the point that you're inviting in a variable degree of uncertainty & bloat, by leaning on a third party.

It would be very interesting to get input from others on what they perceive as the best path forward, in terms of the technicals.

I wonder if a lightweight WebRTC implemention might be a reasonable starting point? Or am I overlooking newer/more relevant browser based comms libraries/APIs?

Reply to this note

Please Login to reply.

Discussion

WebRTC for the audio portion seems like a great starting point.