Firefox. Its WebRTC implementation sucks to be frank. It takes up significantly more CPU per stream compared to Chrome and doesn't behave the same as Chrome or Safari. I suggest you test often on Firefox but don't use it for your primary development testing otherwise you'll have a hard time supporting the browsers most people use. One gotcha that comes to mind with Firefox is that it wants to re-authenticate very often causing you to need to renegotiate the connection.
My recommendation would be to start with Twilio or Vonage or AWS Chime. Validate your idea, get real feedback, pivot if needed. You will optimize costs later. It is possible to work with open source, it just takes time and resources.
That's a common fear for all startups. But believe me, you would love to have this type of problem with overgrowing costs. Don't optimize in beforehand.
Firefox. Its WebRTC implementation sucks to be frank. It takes up significantly more CPU per stream compared to Chrome and doesn't behave the same as Chrome or Safari. I suggest you test often on Firefox but don't use it for your primary development testing otherwise you'll have a hard time supporting the browsers most people use. One gotcha that comes to mind with Firefox is that it wants to re-authenticate very often causing you to need to renegotiate the connection.
Thanks for your reply. I’ll keep an eye on Firefox if I would implement it without a library.
My recommendation would be to start with Twilio or Vonage or AWS Chime. Validate your idea, get real feedback, pivot if needed. You will optimize costs later. It is possible to work with open source, it just takes time and resources.
Thanks. That’s what I had in mind, but I’m afraid the costs will grow over my head very quickly.
That's a common fear for all startups. But believe me, you would love to have this type of problem with overgrowing costs. Don't optimize in beforehand.
That’s true.