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

61–69 of 69 posts

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

#61

Post by maehwasu »

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.

It's not about whether someone else would build this. It's about whether Apple will take draconian steps to stop any of the hotloaders from working.

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

#62

Post by madeofpalk »

andrewljohnson wrote: post #23
doe88 wrote: post #21

Earlier quoted context omitted.

> but updating JavaScript code is explicitly permitted by the iOS Developer Agreement [1]. With the following caveat though: [3.3.2] 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 as submitted to the App Store.

Yep, "feature flipping" can lead to app rejections and getting booted from the store. * If the AppHub founders think this is a real danger, then you'd expect bold and strenuous documentation. * But, I wonder if the AppHub authors believe that people should ignore this rule, because practically speaking it's hard to get caught. They wouldn't say so, of course, because encouraging people to break Apple ToS is illegal.

The 'AppHub' stack looks good and can solve lots of problems.

However I think advertising it as a mechanism to get around the App Store review process is a quick way to get noticed by Apple, and not in a good way.

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

#64

Post by bigiain »

arbesfeld wrote: post #57
volaski wrote: post #56

The problem with this is not if Apple will allow it or not, but the uncertainty, which is deadly for a platform. No developer who take themselves seriously will want to depend on a platform that may go away. Good for you if Apple lets you get away with it, but that doesn't mean it will be like that forever, nor does it mean all apps using this approach will be accepted. It's case by case, and it's already shitty as i…

AppHub cofounder here -- I'm glad you brought this up. A developer who chooses to use AppHub is not depending on the platform. If AppHub goes away (which we hope will never happen!), our iOS SDK defaults to using the App Store build. Moreover, developers can implement their own "AppHub server" if they so choose, so they're not locked in to using our service. We're excited to open source the iOS SDK when we launch to…

My uncertainty is more around what Apple's going to do the first time someone publishes a free FlappyBird clone, then when it's got several million or tens of million downloads magically turns it into a spambot or a million-strong pocket DDoS zombie army.

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

#65

Post by robmcm »

awinder wrote: post #54
teacup50 wrote: post #34

Earlier quoted context omitted.

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.

Couldn't this also aide in correcting regressions at the same time?

Yes it's a double edged sword, in most cases I would favor the ability to update and fix the application without having to force users to manually install an update.

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

#66

Post by mokkun »

teacup50 wrote: post #34
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.

Totally agree with this. As a dev it might sound like a cool thing, but as a user it sucks. Many, many times I found myself not updating an app because I won't agree with the changes (UI, new features, etc) or new permissions that were required.

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

#67

Post by teacup50 »

awinder wrote: post #54
teacup50 wrote: post #34

Earlier quoted context omitted.

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.

Couldn't this also aide in correcting regressions at the same time?

Yes, but as a developer, you're less likely to ship regressions in the first place if your deployment process involves more structure (beta testing, internal code freezes, release branches containing only bug fixes, etc) than 'git push'.

Of course, that runs counter to the "continual deployment" idea popular in web circles, but that's the entire point.

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

#68

Post by awinder »

teacup50 wrote: post #67
awinder wrote: post #54

Earlier quoted context omitted.

Couldn't this also aide in correcting regressions at the same time?

Yes, but as a developer, you're less likely to ship regressions in the first place if your deployment process involves more structure (beta testing, internal code freezes, release branches containing only bug fixes, etc) than 'git push'. Of course, that runs counter to the "continual deployment" idea popular in web circles, but that's the entire point .

This doesn't prescribe which branch you do the git push to though. I'm sure you could just as easily set up a branching scheme where you went through testing and internal releases, and launched new code off a stable branchline

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

#69

Post by markcerqueira »

s73v3r wrote: post #49
markcerqueira wrote: post #29

Earlier quoted context omitted.

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.

"Yes, but if AppHub didn't build this, someone else would." What exactly does that mean? My statement doesn't change just because someone else made it.

It means that this isn't a mind-boggling amazing idea. This is like taking A/B testing to its logical extreme where you can just inject new tests (code) into an existing product.

Also, since you were so kind to reply, why don't you explain what this means: "use it to steal information of a user, or post dick pics all over the app."

Thanks!

Post reply on HN