For the few things you cannot achieve with the Accessibility API's there are ways to post events directly to an app - even though CGEventPostToPid is mostly broken when used on its own. These require a combination of CGEventPostToPid and CGEventTapCreateForPid. (I have done a lot of this stuff in my BetterTouchTool app)

One of BetterTouchTool's first features ~17 years ago was trackpad gesture customization, it is still one of the most important things you can do with BTT! ;-) You'd just need to assign the "Move Right a Space (without animation)" and "Move Left a Space (without animation)" actions to trackpad gestures in BTT.

One advantage of BTT's current implementation is that it still allows you to move windows to the next/previous space while dragging them and simultaneously executing the "Move Left / Right a space" action. In that case there will be an animation but it will at least work.

- somebody wants to push his app with fake reviews, however that would be easy to detect / trace back. Thus that person buys additional positive fake reviews for other apps (that are not in competition with his apps). This makes it really hard to tell which of the apps "purchased" the fake reviews.

I‘m the developer of BetterSnapTool & BTT and have also discovered & reported these fake reviews to Apple about three weeks ago on July 2. They are investigating and keep deleting (some of) the fake reviews, but I have no idea who is responsible for them or what they want to achieve

You can add feature requests there, it should be pretty simple to extend BTT to support the remaining required features.

I have also recently been approached by shady companies trying to buy my app (I'd never do that) - maybe they are currently targeting apps that require special permissions?

You can add feature requests there, it should be pretty simple to extend BTT to support the remaining required features.

I‘m absolutely fine with having the ML run on my Desktop as long as it syncs to the phone as well.

Whether Web Bluetooth, Web HID etc should be implemented in a browser engine is really irrelevant in this context - but the thing is they CAN be implemented in a browser engine. So can pretty much any native functionality currently guarded by the App Store.

I don’t think Apple can tell alternative browser engines what features it will allow and which not. Or is there something in the EU regulation that says browser engines must follow a standard?