Assuming you're referring to the fact that it doesn't work on all browsers, it's literally a beta.
It clearly states that it's for Chrome/Edge/Safari only, and not for mobile. But it also says at the bottom:
> Support for additional languages, browsers, and platforms will be expanded over time.
I think it's totally fair that a beta has support for limited browsers, in order to get it out faster. Just like it's only in English for now as well, although that will obviously expand too.
If it's not available for Firefox or Android when it leaves beta, then yes it's a problem. But an English-only beta with limited compatibility is one of the things betas are for. It's an appropriate setting of expectations.
From first-hand experience, I've seen it happen in SaaS orgs with (diplomatically speaking) "unsophisticated-but-confident" userbases seeking to reduce support-costs. The kind of SaaS where the paying customer is a business - and where the users' eyes glaze-over any warning banner or message but eagerly call the SaaS support number for entirely unrelated issues with Outlook; so outright blocking unsupported browsers/clients reduces the support burden.
(I'm not defending this practice; I'm strongly opposed to it)
----
Another (also, unfortunately, from first-hand experience) reason is a (very) non-technical project leader will write up a (semi-reasonable) brief Jira ticket like "Our SaaS product doesn't work in Firefox; until we invest in supporting Firefox we'll just direct users to use a supported browser" - but the ticket gets assigned to a particular kind of remote contractor SWE who never challenges higher-ups or says "this is a bad idea" - who'll interpret the part about "we'll direct users to use a supported browser" as "block unsupported browsers".
Because they're probably not undergoing a formal QA process yet and Apple doesn't want to deal with bug reports and bad press about how its beta is janky/buggy/sucky in other browsers. This is pretty standard stuff for webapps doing a phased rollout of browsers -- it's not anything unique to Apple.
Just because people in this thread have found workarounds to get it to launch in Firefox doesn't mean there aren't still a bunch of bugs there, that Apple is aware of but doesn't want marring the user experience yet.
It's more about Apple's rotten philosophy and hubris. Like how they pit teens against each other by artificially restricting their proprietary messaging system.
It's about the attitude. WE (Apple) gets to decide what how and where you use our products and services that you pay for. YOU (the paying user) will do as we say.
Also, what is with the fanboy defense of the richest corporation in the world? If they want to defend their shitty sales tactics they can afford to pay for it.
Literally every software developer makes decisions about what platforms to support and not, and when. This is not an Apple thing.
Also:
> Please don't post insinuations about astroturfing, shilling, brigading, foreign agents, and the like. It degrades discussion and is usually mistaken.
It clearly states that it's for Chrome/Edge/Safari only, and not for mobile. But it also says at the bottom:
> Support for additional languages, browsers, and platforms will be expanded over time.
I think it's totally fair that a beta has support for limited browsers, in order to get it out faster. Just like it's only in English for now as well, although that will obviously expand too.
If it's not available for Firefox or Android when it leaves beta, then yes it's a problem. But an English-only beta with limited compatibility is one of the things betas are for. It's an appropriate setting of expectations.