21 ms·
The most interesting part is that Apple seems to be cool with this: > Does Apple permit this? > Yes! Section 3.3.2 of the iOS Developer Program allows it "pro
by arasmussen 11y ago
The most interesting part is that Apple seems to be cool with this:
> Does Apple permit this?
> Yes! Section 3.3.2 of the iOS Developer Program allows it "provided that such scripts and code do not change the primary purpose of the Application by providing features or functionality that are inconsistent with the intended and advertised purpose of the Application."
I really, really hope this doesn't go away.
- maz-dev 11y agoI use this feature with a Meteor app and it's really nice. Just be sure to not load a corrupted or crashing bundle, else your user will need to reinstall the app. Apple is allowing this because JS is sandboxed, so I guess it's here to stay.
- martinald 11y agoI wouldn't be so sure. If this starts getting real traction then it is a huge leap over the native development process. Which ironically is all Apple's fault for it taking so long for them to approve updates. Having said that Apple seems slightly more chilled now Cook's in charge. Also, this is react native, so it is only sandboxed in the way any other app is. The JS->ObjC bridge can do pretty much anything a native app can do so I don't think the JS thing makes much difference. I think really it's in there so people can update webviews of content without having to resubmit the whole app. I don't think this is the spirit of that rule. Would be pleasantly surprised if not though.