Whereby is, as far as I can tell, completely owned by a Norwegian registered company.
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.
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...
Just some feedback. I think the free tier was a little unclear.
> Free
> Personal use
> 1 user
> 1 meeting room
I have trouble reading this. It's as if I coule only create one room for myself without having anybody to chat with.
A p2p room can have 4 total people in it. So say you plus 3 concurrent guests, none of those guests need any account or "user".
Indeed even you don't have to log in after you've created the room if you leave it unlocked. :)
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 :)
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.
There is currently a bug with audio, where it'll crash in Safari, -- and we have had some issues reconnects that was more our fault (though Firefox and Chrome is much more forgiving). We have a workaround for the first, and will be doing a fix for the second once we're reasonably sure it won't regress other browsers.
Is it any of those issues you talk about? Or is it something else? (I'm not personally familiar with the Safari issues, btw, since I'm a Linux user, but I keep an eye on Firefox and Chromium-based browsers)
I will play with it today and send bug report. Might help you guys out, I really like it otherwise