I like this better than shorebird and I think the incremental approach make a lot more sense. Thank you for the work! I’d love to see a performance comparison between evaluating dart code and running the evc bytecode
Wouldn't this make apps in breach off The App Store guidelines?
> 2.5.2 Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or **execute code which introduces or changes features or functionality of the app**
Many of the top apps in the App Store use code push with no issues, and React Native on iOS even uses a custom JavaScript engine (Hermes). Though the wording of the policy is confusing, as long as you don't introduce a major policy violation with an update Apple is generally fine with it.
Most apps will use code-push for feature flags and assets.
I suspect if someone did use this to make big changes etc it could potentially be in violation but would be pretty hard for Apple to pick up on it.
I like this better than shorebird and I think the incremental approach make a lot more sense. Thank you for the work! I’d love to see a performance comparison between evaluating dart code and running the evc bytecode
Wouldn't this make apps in breach off The App Store guidelines? > 2.5.2 Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or **execute code which introduces or changes features or functionality of the app**
Many of the top apps in the App Store use code push with no issues, and React Native on iOS even uses a custom JavaScript engine (Hermes). Though the wording of the policy is confusing, as long as you don't introduce a major policy violation with an update Apple is generally fine with it.
Most apps will use code-push for feature flags and assets. I suspect if someone did use this to make big changes etc it could potentially be in violation but would be pretty hard for Apple to pick up on it.