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

Apple allows hot code push for JS downloaded and run by WebKit

meteor.com

Post reply on HN
Print view View original

51–60 of 74 posts

Re: Apple allows hot code push for JS downloaded and run by WebKit

#51

Post by kentonv »

bribri wrote: post #49
kentonv wrote: post #41

Earlier quoted context omitted.

No, "sites" would imply "web sites that you could just as easily open in Safari", which is not what they're talking about here. They're talking about implementing an app in Javascript stored locally (still accessible when you have no connectivity), and then being able to download updates to that code directly from the developer rather than through the app store. A lot of people (including myself) legitimately wondere…

OK Great, Meteor uses regular HTML5 to store things in the app cache (that you could just as easily do in Safari by the way) and Apple's webview complies with the HTML5 standard. I guess I'm just not that surprised that Apple allows the use of standard HTML5 and UIWebview behaves like a browser.

No, that's not what Meteor does.

Re: Apple allows hot code push for JS downloaded and run by WebKit

#52

Post by aikah »

kentonv wrote: post #41
bribri wrote: post #26

Earlier quoted context omitted.

Better title suggestion: Apple allows sites to be opened in webview

No, "sites" would imply "web sites that you could just as easily open in Safari", which is not what they're talking about here. They're talking about implementing an app in Javascript stored locally (still accessible when you have no connectivity), and then being able to download updates to that code directly from the developer rather than through the app store. A lot of people (including myself) legitimately wondere…

When you use a webview you're basically displaying HTML content period. granted it's not on the "web",that's what it is.If webviews implement specs correctly then what they does is basically what any browsers do.And the title IS link baiting.

Re: Apple allows hot code push for JS downloaded and run by WebKit

#53

Post by mratzloff »

dubcanada wrote: post #48
debergalis wrote: post #47

Earlier quoted context omitted.

[i work at meteor] Meteor's hot code push on mobile is more sophisticated than this. When you deploy a new version of a Meteor app, clients fetch and save the new client JavaScript bundle along with its static assets. Future launches of the installed app immediately run new code (even offline) without first requiring a round trip to a server.

How can something that is offline somehow get new code? Besides that it sounds exactly like a website.

He's saying it caches the JS and all assets when online so that they can continue to function offline.

Re: Apple allows hot code push for JS downloaded and run by WebKit

#54

Post by bribri »

kentonv wrote: post #51
bribri wrote: post #49

Earlier quoted context omitted.

OK Great, Meteor uses regular HTML5 to store things in the app cache (that you could just as easily do in Safari by the way) and Apple's webview complies with the HTML5 standard. I guess I'm just not that surprised that Apple allows the use of standard HTML5 and UIWebview behaves like a browser.

No, that's not what Meteor does.

http://docs.meteor.com/#appcache " The appcache package stores the static parts of a Meteor application (the client side Javascript, HTML, CSS, and images) in the browser's application cache [...] Hot code pushes are loaded by the browser in the background while the app continues to run. Once the new code has been fully loaded the browser is able to switch over to the new code quickly."

https://github.com/meteor/meteor/wiki/AppCache

"The appcache package is designed to support Meteor's hot code reload feature. "

Re: Apple allows hot code push for JS downloaded and run by WebKit

#55

Post by dang »

redbergy wrote: post #23
dang wrote: post #19

Earlier quoted context omitted.

I don't see it? In cases of misleading or linkbait titles we're glad to hear suggestions for a better title. There are too many posts here for us to correct everything correctly, so help is welcome.

While the title isn't necessarily false, it's misleading link bait because people click on it thinking that Apple is now allowing us to push out Swift/Objective-C updates in-app. It's more feasible than ever that this could happen now since they've added the ability to include frameworks inside of your apps where previously you couldn't. The link is referring to using HTML/JS/CSS to update apps, which has been possib…

Ok, we changed the title to something close to that but with more language from the article itself.

If that's not good enough we can edit it again.

Re: Apple allows hot code push for JS downloaded and run by WebKit

#56

Post by imslavko »

bribri wrote: post #54
kentonv wrote: post #51

Earlier quoted context omitted.

No, that's not what Meteor does.

http://docs.meteor.com/#appcache " The appcache package stores the static parts of a Meteor application (the client side Javascript, HTML, CSS, and images) in the browser's application cache [...] Hot code pushes are loaded by the browser in the background while the app continues to run. Once the new code has been fully loaded the browser is able to switch over to the new code quickly." https://github.com/meteor/mete…

Appcache is a completely different feature that existed in Meteor long long time ago.

The new feature that works in Phonegap integration is storing the application data in App's local storage (not browser's). Not only these files are accessible before the browser is loaded but also they don't need to be downloaded first time, the initial code is shipped with the standard app bundle.

(I work at Meteor on this exact feature)

Re: Apple allows hot code push for JS downloaded and run by WebKit

#57

Post by bribri »

dang wrote: post #55
redbergy wrote: post #23

Earlier quoted context omitted.

While the title isn't necessarily false, it's misleading link bait because people click on it thinking that Apple is now allowing us to push out Swift/Objective-C updates in-app. It's more feasible than ever that this could happen now since they've added the ability to include frameworks inside of your apps where previously you couldn't. The link is referring to using HTML/JS/CSS to update apps, which has been possib…

Ok, we changed the title to something close to that but with more language from the article itself. If that's not good enough we can edit it again.

I would make it say 'Apple allows hot code push for JS downloaded and run by WebKit'

Re: Apple allows hot code push for JS downloaded and run by WebKit

#58

Post by dang »

bribri wrote: post #57
dang wrote: post #55

Earlier quoted context omitted.

Ok, we changed the title to something close to that but with more language from the article itself. If that's not good enough we can edit it again.

I would make it say 'Apple allows hot code push for JS downloaded and run by WebKit'

Ok, let's try that.

Re: Apple allows hot code push for JS downloaded and run by WebKit

#59

Post by oceanstone »

debergalis wrote: post #47
rubyn00bie wrote: post #39

In other words: webpages function as expected on iOS. ... Not to blame the meteor folks for writing it, if they were getting asked it... But wow. I personally think the title is a bit click-baity, but that's because it's not really hot code push. It's loading a web view. If this was hot loading new native code that'd be newsworthy or at least interesting.

[i work at meteor] Meteor's hot code push on mobile is more sophisticated than this. When you deploy a new version of a Meteor app, clients fetch and save the new client JavaScript bundle along with its static assets. Future launches of the installed app immediately run new code (even offline) without first requiring a round trip to a server.

That sounds awesome. Are you using localStorage?

Re: Apple allows hot code push for JS downloaded and run by WebKit

#60

Post by EGreg »

dozy wrote: post #38

I once worked for Pyxis Mobile (now Verivo Inc.) which touted a platform which would provide you with native iOS, Android, and BlackBerry (years ago..) apps, which would build themselves at run time based on a database/app meta data. This allowed apps to completely change themselves without a resubmission, while being in-line with Apple's guidelines, and technically be purely native. Between lazy loading and the fact…

Have you ever done A/B testing?

That's the real value if you want to actually measure things and improve them. Maybe doing so can even minimize spectacular bugs when you push. And how would you accomplish this A/B iteration with weekly pushes to everyone?

Post reply on HN