Chrome works. Safari cannot provide the same system-audio path.

We found a browser limitation that changes the product promise.

Speechara.Ai can capture the system-audio path we need in Chrome and Chromium-based browsers such as Edge. Safari currently does not expose the same path to a web app, so the workflow is not available there in the same way.

This is not a bug in our interface. It is a platform capability mismatch, but users experience it as product inconsistency.

The honest guidance for now is to use Chrome or Edge. That is technically simple, but it is a frustrating sentence to put in onboarding, especially for Mac users who naturally open Safari first.

We are weighing three options: detect Safari and explain the limitation early, build a desktop fallback, or design a Safari-specific workflow with a narrower promise.

How do you handle a browser or platform limitation when the product works well in one environment but cannot support a core workflow in another? Do you detect it early, narrow the promise, or invest in an alternative UX?