search

Azure / Communication

Azure Communication Services - SDKs and Release Notes
MIT License
320 stars 99 forks source link

Feature Request - Compatible Browser check in Web SDK #418

Open ghost opened 2 years ago

ghost commented 2 years ago

I'm currently working on a project that is integrating the Web SDK and I'd like a reliable method for determining browser compatibility. Ideally the web SDK's would provide a compatibility API.

Current Behavior Use an incompatible browser like Firefox

  1. User taps on button to join meeting
  2. User enters name to use during meeting
  3. User confirms entry
  4. callAgent is created by client app
  5. Fails with unsupported browser exception

Desired behavior

  1. Client SDK invokes API method
  2. If browser is compatible
    • Perform Join meeting flow
  3. Else browser is incompatible
    • Direct user to meeting alternative

Current Solution We could use the check that the Hero example uses, treat only Firefox browser as incompatible

However, the documentation describes more than just Firefox being incompatible.

Browsing the analytics reports for our app, about a third of the reported users' browsers are "Unknown"

eamreyes commented 2 years ago

Subscribing as my previous account was deleted.

davideberlein commented 2 years ago

We have the same problem. The funny thing is that you recently introduced the Environment API to be able to check the browser compatibility but that API actually needs a CallClient first. Also having some better docs on the flags of the environment API would also be helpful to determine which flag to best use (once the bug is fixed)

akania commented 1 year ago

Environment API can be instantiated from CallClient instance, and creation of that one, should not be limited by any os/browser/version combination - once created, you can check if current combination is supported before creating callAgent let me know if that helps