The web client would be for most users, the native iOS/macOS client would be for the smaller group that manages the deployments (would be one person at a company or in a friend group). I'm working on cross-plat Swift strategies to bring this to Windows later.
It's a good point, I'll find a good way to start earlier with cross-plat deployment management. Between the two of us we have strong fullstack skills in web and iOS/Apple ecosystem. Apple App Store distribution and IAP are a strong part of our typical app strategies (I'm able to drive huge user growth via App Store) but this approach for this idea needs more thought because the deploy-manager person for this app wouldn't be the one we'd charge IAP to. I'm not actually sure how to make money off this idea yet.
It's also potentially linux-runnable (the management tools) with a native apple frontend, then later can explore bringing to win/web
I've been moving more of my iOS app core biz logic to JS and exploring cross plat Swift for running more across web and windows, while still leaning hard into the nice parts of Apple ecosystem, so that whatever solution I find for this is easier
We're also doing an app using https://github.com/live-codes/livecodes to move a lot more languages/envs capability into the client which might enable some good web and ios cross plat capabilities.
Anyway besides the platform question, interested in any other feedback from anyone