A Whereby-developer here. It's awesome you recommend us. <3 But we'll also kill your CPU ^_^
You can turn on "mobile mode" in advanced device settings, and it should be a bit better. But we're a bit limited in how CPU-friendly we really can be, living in the browser. Not that we can't improve, there's certainly extra tricks we could try - but not easily without also lowering fps and resolution.
I don't think "low resource use" is a big selling-argument for our product. Video can be quite heavy.
Actually, if you are using 4+ rooms, we will in many cases be better than some other webrtc services because we for these bigger rooms use a server in the middle to distribute all the streams. That will result in lower resource use. You only encode and send once, and it is distributed by the server. But if other webrtc kills CPU on 4 or less, we probably won't be much better.
This "more than 4 room" is not p2p and end-to-end encrypted, since the server (SFU) needs to read and change some headers. So it is a tradeoff. There's now "insertable streams" which allow you to do encryption on the media client side, but it's a test for now: https://webrtchacks.com/true-end-to-end-encryption-with-webr...
Hey! I've been using Whereby at work for a while and it's great.
However, I should mention that it's not possible to join calls through the mobile app (as far as I can tell), and the web app on mobile wouldn't capture my Bluetooth headset's audio properly somehow.
Again, thanks for the great work. Just thought I'd let you know :)
Thanks! It is very valuable with feedback like this, even if in this case we're painfully aware of it. :)
I was working on fixing up that when COVID-19 hit. Now we're trying to stamp out more obscure audio+video bugs (like bluetooth, which can be unreliable). We're in process of hiring a few more people so we can hopefully put someone on caring more for the non-logged in mobile app experience.
You do get a join button once you've logged in. But I must confess it is not a good experience by default. It used to be on the top of the priority list, but then scaling and any video/audio issues jumped to the top.
You can turn on "mobile mode" in advanced device settings, and it should be a bit better. But we're a bit limited in how CPU-friendly we really can be, living in the browser. Not that we can't improve, there's certainly extra tricks we could try - but not easily without also lowering fps and resolution.
I don't think "low resource use" is a big selling-argument for our product. Video can be quite heavy.