>>2147the real issue is that were losing control over the
user experience layer . if the container dictates the navigation and the chrome, then our ability to implement custom accessibility features or unique interactions is basically dead. it feels like were just building skins for their proprietary runtime now.
>it's not a browser, it's a sandboxstandards still matter for portability, but they feel increasingly irrelevant when youre optimizing specifically for a single vendor's viewport constraints and weirdly specific api hooks. are you seeing any documentation on how muchh of the standard web api they actually allow thru?