Our main will have to be a RoA app, going down the route of a second, zero egress, app isn’t cutting it, the macro name change is unworkable. However, the revenue change is forcing us to jump.
We embed draw.io diagrams from cloud storage, GDrive, OneDrive, etc. The auth has to be through a known domain server. Currently, the idea is to create another forge app that does have optional egress that all 60k installs of the main app have to install and then ask them all to migrate those embedded diagrams.
We have diagram generation via OpenAI, that’ll have to go, it can’t be done within Forge.
There’s no web socket support, so we lose real-time collaboration, falling back to a slowly, polling update. I can continue the list.
Our only way to avoid a support meltdown when this is launched is to ensure it’s a manual admin update and write “DO NOT PRESS UPDATE” in the release notes.
The only solution for us is if the host can enforce RoA for apps which optional egress and switch all that egress off. So, if the app is on isolated cloud (for example) an app vendor would have to tick “works with zero egress” on the app and enforces that the optional egress are no longer optional. Same for public cloud, the user either sets zero egress per app or for all apps.