No friction points that I can think of off the top of my head. Biggest upside is that it just works seamlessly. When switching between code bases, pulling PR’s for review, etc. it’s quite nice not worry about things like whether you have access to the iOS emulator.
Team is primarily M1 MBPs.
Backend APIs are .NET 6 Web API in C#. Deploy to AWS Graviton2 instances. Build in GitHub Actions and AWS CodePipeline (yuck!).
Frontend is a mix of React (Next.js, externally facing) and Vue (internal tooling)
> No friction points that I can think of...
Well...
I use both VS Code and Rider. I'd say that OmniSharp is a friction point because it's still just a bit janky in some edge cases.
As long as a team is willing to pay for Rider (100% worth it), dev experience is great. If not, just be prepared to get used to the quirks of C# on VS Code with OmniSharp and get comfortable with the CLI (which you should anyways). The modern CLI is so good compared to old msbuild.
I have not personally used VS Mac, but from what I've seen of it (other devs that used it), it looks like a downgrade. But devs using VS Mac all switched to Rider a few months back and never looked back.