Comments on: With WebRTC, better stick as close as possible to the requirements, architecture and implementation of Google Meet https://bloggeek.me/webrtc-stick-to-architecture-of-google-meet/ The leading authority on WebRTC Mon, 19 Sep 2022 20:44:33 +0000 hourly 1 By: Tsahi Levent-Levi https://bloggeek.me/webrtc-stick-to-architecture-of-google-meet/#comment-154280 Mon, 19 Sep 2022 20:44:33 +0000 https://bloggeek.me/?p=73421#comment-154280 In reply to Daniel.

Try to out-do Google Meet in video quality or voice quality for one. It is doable to some extent, but you’ll need to really know what you’re doing.

Then there’s live streaming. Again, doable, but not in the main target focus of Google. So you need more expertise here.

Cloud gaming. Especially now that Stadia has lots its shine for Google.

]]> By: Daniel https://bloggeek.me/webrtc-stick-to-architecture-of-google-meet/#comment-154279 Mon, 19 Sep 2022 20:40:34 +0000 https://bloggeek.me/?p=73421#comment-154279 The premise of the article makes sense to
me, but I feel like I'm missing something.
WebRTC allows us to transport audio and
video from one consumer electronic device
over the Internet to another at real time
speeds sufficient to facilitate conversations.
What else is there? To put my question
another way, what could someone try to do
with WebRTC that is not close to the
requirements architecture and
implementation of Google Meet? Does
anyone have any examples of what
specifically the author is advising us not to do?

]]> By: Philipp Hancke https://bloggeek.me/webrtc-stick-to-architecture-of-google-meet/#comment-154274 Mon, 19 Sep 2022 18:53:07 +0000 https://bloggeek.me/?p=73421#comment-154274 Tsahi,

I feel like you are sub-blogging about me!

But yeah, the teams who can go against the tide are rare. I am quite fortunate to know two 😉

]]>