Updated iOS Developer Agreement in 3..2..1..
AppHub – Update React Native Apps Without Re-Submitting to Apple
11–20 of 69 posts
Re: AppHub – Update React Native Apps Without Re-Submitting to Apple
#12Technically, this looks like a cool hack.
I've never found submitting an app for app review to be that big of a deal, if your app is well designed, useful, and not negligent or malicious toward user needs.
Your FAQ says what you're doing is explicitly permitted by Apple, and points to section 3.3.2 of the iOS Developer Program Information document.
But what about section 3.3.3?
3.3.3
Without Apple’s prior written approval or as permitted
under Section 3.3.25 (In App Purchase API), an
Application may not provide, unlock or enable
additional features or functionality through
distribution mechanisms other than the App Store
or VPP/B2B Program Site
Again cool hack but it will be interesting to see if it gets out of the starting gate.
Re: AppHub – Update React Native Apps Without Re-Submitting to Apple
#13AppHub co-founder here, we realize that this is something that would seem to be prohibited by Apple, but updating JavaScript code is explicitly permitted by the iOS Developer Agreement [1]. This same technology is used by Meteor [2], Trigger.io [3], and Adobe Hydration [4], and also used by Facebook and Palantir [5] in their apps. [1] https://developer.apple.com/programs/ios/information/iOS_Pro... [2] http://info.met…
It looks like you're sending the whole JS bundle when doing a deploy, do you think you'll support async loading? Would help with massive applications and other speed related optimizations.
Re: AppHub – Update React Native Apps Without Re-Submitting to Apple
#14I see that lasting almost three weeks before Apple shut it down (assuming anyone uses it...)
Apparently it is within the terms of the iOS developer program? They list that in their FAQ near the bottom of the page
They are pointing to just one paragraph of the agreement and ignoring other paragraphs that say the opposite.
Re: AppHub – Update React Native Apps Without Re-Submitting to Apple
#15AppHub co-founder here, we realize that this is something that would seem to be prohibited by Apple, but updating JavaScript code is explicitly permitted by the iOS Developer Agreement [1]. This same technology is used by Meteor [2], Trigger.io [3], and Adobe Hydration [4], and also used by Facebook and Palantir [5] in their apps. [1] https://developer.apple.com/programs/ios/information/iOS_Pro... [2] http://info.met…
It looks like you're sending the whole JS bundle when doing a deploy, do you think you'll support async loading? Would help with massive applications and other speed related optimizations.
Great question! Our iOS SDK asynchronously downloads new JS bundles and images, and then loads the updates when your app is restarted. There are definitely some speed optimizations that we can make in the future, such as using diffs to apply updates.
We're excited to open source the iOS SDK in the future so that everyone can take a look and contribute.
Re: AppHub – Update React Native Apps Without Re-Submitting to Apple
#16Technically, this looks like a cool hack. I've never found submitting an app for app review to be that big of a deal, if your app is well designed, useful, and not negligent or malicious toward user needs. Your FAQ says what you're doing is explicitly permitted by Apple, and points to section 3.3.2 of the iOS Developer Program Information document. But what about section 3.3.3? 3.3.3 Without Apple’s prior written app…
Just to reiterate, it seems legit reading from
http://image.slidesharecdn.com/real-worldreactnativees7-1506...
Now, to add something to the matter, "direct update" is something that Apple already hosts in its App Store through Cordova apps and its commercial versions (i.e. MobileFirst) https://www.apple.com/pr/library/2014/12/10Apple-and-IBM-Del...
Not sure how many React Native projects are hosting their bundles outside theirs apps in the wild, but there are already apps released on the store (as per Facebook Groups, Ads Manager).
Still, I agree things might change (on the Apple's side).
Re: AppHub – Update React Native Apps Without Re-Submitting to Apple
#17AppHub co-founder here, we realize that this is something that would seem to be prohibited by Apple, but updating JavaScript code is explicitly permitted by the iOS Developer Agreement [1]. This same technology is used by Meteor [2], Trigger.io [3], and Adobe Hydration [4], and also used by Facebook and Palantir [5] in their apps. [1] https://developer.apple.com/programs/ios/information/iOS_Pro... [2] http://info.met…
"Use git push to update your app without re-submitting to Apple." - That's the prominent tagline in your home page. Isn't that too direct? One suggestion - wording it without being too obvious could prevent your from a possible ban, and an even worser outcome of Apple changing their policies.
Re: AppHub – Update React Native Apps Without Re-Submitting to Apple
#18Technically, this looks like a cool hack. I've never found submitting an app for app review to be that big of a deal, if your app is well designed, useful, and not negligent or malicious toward user needs. Your FAQ says what you're doing is explicitly permitted by Apple, and points to section 3.3.2 of the iOS Developer Program Information document. But what about section 3.3.3? 3.3.3 Without Apple’s prior written app…
AppHub is not trying to circumvent the Apple release process, rather, we want to make distributing updates as frictionless as possible. The main advantages we give developers are instant updates and staged rollouts (deploying new features to a percentage of users).
Glad you pointed out Section 3.3.3 of the Developer Agreement. From our understanding, it is intended to prevent developers from trying to avoid the App Store fees. As always, it will be up to developers to follow Apple's guidelines in their iOS apps.
Re: AppHub – Update React Native Apps Without Re-Submitting to Apple
#19Technically, this looks like a cool hack. I've never found submitting an app for app review to be that big of a deal, if your app is well designed, useful, and not negligent or malicious toward user needs. Your FAQ says what you're doing is explicitly permitted by Apple, and points to section 3.3.2 of the iOS Developer Program Information document. But what about section 3.3.3? 3.3.3 Without Apple’s prior written app…
Just to reiterate, it seems legit reading from http://image.slidesharecdn.com/real-worldreactnativees7-1506... Now, to add something to the matter, "direct update" is something that Apple already hosts in its App Store through Cordova apps and its commercial versions (i.e. MobileFirst) https://www.apple.com/pr/library/2014/12/10Apple-and-IBM-Del... Not sure how many React Native projects are hosting their bundles out…
Yeah I think I'd like to see this work. If it's used for good things. Not sure who is right about whether it's allowed in the current terms; it depends on how you read it. My prediction though is that Apple will see it as enough of a threat to their control that they will either disallow it outright under their own reading of the terms, or they will tweak the terms to disallow it. But then... need I say... I could be wrong.
Re: AppHub – Update React Native Apps Without Re-Submitting to Apple
#20Earlier quoted context omitted.
Just to reiterate, it seems legit reading from http://image.slidesharecdn.com/real-worldreactnativees7-1506... Now, to add something to the matter, "direct update" is something that Apple already hosts in its App Store through Cordova apps and its commercial versions (i.e. MobileFirst) https://www.apple.com/pr/library/2014/12/10Apple-and-IBM-Del... Not sure how many React Native projects are hosting their bundles out…
Yeah I think I'd like to see this work. If it's used for good things. Not sure who is right about whether it's allowed in the current terms; it depends on how you read it. My prediction though is that Apple will see it as enough of a threat to their control that they will either disallow it outright under their own reading of the terms, or they will tweak the terms to disallow it. But then... need I say... I could be…
Same sentiment here. Let's hope you're wrong! :)
Anyway, there's no way they could lose (too much) control. The "native" part of the apps is still subject to resubmission. The "react native" part is mostly UI layer/composition and business logic.