Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AppHub – Update React Native Apps Without Re-Submitting to Apple

apphub.io

Post reply on HN
Print view View original

31–40 of 69 posts

Re: AppHub – Update React Native Apps Without Re-Submitting to Apple

#31

Post by jsierles »

markcerqueira wrote: post #29
s73v3r wrote: post #26

And this is why we can't have nice things. Someone is going to submit a React Native app to the App Store, use this bullshit to bypass the update review, and either use it to steal information of a user, or post dick pics all over the app.

Yes, but if AppHub didn't build this, someone else would. Just because something isn't the "safest" idea doesn't mean we shouldn't stop experimenting. Also, how would this make it easier to steal user information or share your stash of dick pics? Sounds like a lot of FUD to me.

Agreed. Amazingly, we released our version of this within the hour: https://reploy.io. And many other frameworks are doing the same thing. http://blog.ionic.io/announcing-ionic-deploy-alpha-update-yo....

Re: AppHub – Update React Native Apps Without Re-Submitting to Apple

#32

Post by s73v3r »

balls187 wrote: post #30
s73v3r wrote: post #28

Earlier quoted context omitted.

This: "Stop waiting weeks for Apple to review your app. Just add our iOS framework and start pushing updates." says otherwise.

The key verbiage is "release" vs "updates." You still have to go through the initial App Store Release process initially. After that, using this framework you can push updates directly, rather than waiting the requisite 5 business days[1]. As an app developer, being able to push updates (read: bug fixes) immediately is a blessing--we live and die by our reviews, and a bad update can cause an avalanche of negative rev…

I really don't see Apple making that distinction.

Re: AppHub – Update React Native Apps Without Re-Submitting to Apple

#33

Post by balls187 »

s73v3r wrote: post #32
balls187 wrote: post #30

Earlier quoted context omitted.

The key verbiage is "release" vs "updates." You still have to go through the initial App Store Release process initially. After that, using this framework you can push updates directly, rather than waiting the requisite 5 business days[1]. As an app developer, being able to push updates (read: bug fixes) immediately is a blessing--we live and die by our reviews, and a bad update can cause an avalanche of negative rev…

I really don't see Apple making that distinction.

Nor do I.

Best case, this is a minor annoyance to Apple, and they don't bother.

Worst case, a bad actor abuses this forcing Apple to immediately pull any and all apps built ontop of this.

For anything other than an MVP, I wouldn't risk it.

Re: AppHub – Update React Native Apps Without Re-Submitting to Apple

#34

Post by teacup50 »

benthehenten wrote: post #7

AppHub 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…

Apple aside, doing this kind of thing silently sucks for users -- one of the benefits of native applications over the web is having control over when updates containing potential regressions are inserted into your workflow.

Re: AppHub – Update React Native Apps Without Re-Submitting to Apple

#35

Post by Touche »

vjeux wrote: post #22
hharnisch wrote: post #13

Earlier quoted context omitted.

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.

Right now React Native packager bundles everything in one file but we're actively working on splitting it into many different files and supporting require.ensure() in order to asynchronously load modules.

Oh, so you're only going to support WebPack? That's disappointing.

Re: AppHub – Update React Native Apps Without Re-Submitting to Apple

#36

Post by skrebbel »

Touche wrote: post #35
vjeux wrote: post #22

Earlier quoted context omitted.

Right now React Native packager bundles everything in one file but we're actively working on splitting it into many different files and supporting require.ensure() in order to asynchronously load modules.

Oh, so you're only going to support WebPack? That's disappointing.

They take pull requests

Re: AppHub – Update React Native Apps Without Re-Submitting to Apple

#39

Post by bryanlarsen »

balls187 wrote: post #33
s73v3r wrote: post #32

Earlier quoted context omitted.

I really don't see Apple making that distinction.

Nor do I. Best case, this is a minor annoyance to Apple, and they don't bother. Worst case, a bad actor abuses this forcing Apple to immediately pull any and all apps built ontop of this. For anything other than an MVP, I wouldn't risk it.

Hopefully AppHub can mitigate the worst case scenario to "you have to fall back to standard Apple update procedures".

Re: AppHub – Update React Native Apps Without Re-Submitting to Apple

#40

Post by spicyj »

Touche wrote: post #35
vjeux wrote: post #22

Earlier quoted context omitted.

Right now React Native packager bundles everything in one file but we're actively working on splitting it into many different files and supporting require.ensure() in order to asynchronously load modules.

Oh, so you're only going to support WebPack? That's disappointing.

No one said anything about webpack. If you have another async module loading syntax you'd prefer I'm sure we'd be happy to look at it.
Post reply on HN