Apple only allows you to access the microphone if you use HTTPS so I had to use Tailscale serve to get a url and I use that.
Distribution is tricky since you’re asking a person to run a web app but fuck Apple’s walled garden.
My one suggestion is to create a style guide for Claude so that the homepage doesn't have Claudeisms.
For example, Claude loves the word hold, which is v annoying. The word "with" is right there.
E.g. "anyone holding its invite link"
Apple is on the W3C comittee that gets to decide on which proposals will become standardized browser APIs. And they use their power there to block API proposals that could make browsers more capable, competing with native apps.
Apple is holding up quite a few useful API proposals, and they won't even suggest any changes to make to the proposals. They just do not want web browsers to be any more capable than they currently are. Apple is literally stifling innovation in favor of their own greed.
What features on the browser are blocked that are preventing your app from being a PWA? Is it one of the many Google supported privacy breaking features no other vendors want to implement?
There are all kinds of small issues. For example, we can't do HDR on iOS for photos in the browser because WebGPU doesn't support it.