Firefox and Safari would probably work for the majority of features but Chrome probably exposes some browser APIs that the rest don't that might make a couple things not work.
For people who know enough to spoof a Chrome user agent, they know enough not to mind if some things break but regular consumers wouldn't know about browser compatibility topics and would blame any irregularities not on their browser but on Snapchat, which is why they choose to display this error rather than let people through.
Yea that's fair, and I totally understand when sites limit to newer (last 2-3 years) versions of browsers or limit to Chrome, Safari, and Firefox.
But to cap it at just Chrome like its 2012 when browser compatibility has come such a long way is likely unnecessary and frankly lazy on their part. I can't think of an API that they definitely would need to use that isn't in Firefox.
This is the torture of writing applications for other people. There’s userCount + 1 opinions on things.
I often have to make notes to remind myself how half the CS team wants it like X but the other half wants Y and to stop oscillating the feature. Sometimes you can’t make everyone happy with a clever solution. Sometimes you get to make everyone equally unhappy.
It’s the debate as old as time: should the website load as best as it can, or should it work perfectly or not at all?
I'd just choose a world with less clip-based frenzied communication and developed some standard of digital stoicism instead of overindulgence that is snapchat and tiktok.
Update: It works totally fine on Firefox if you use an extension to lie about your user agent. What a joke.