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 wondered if Apple permits this, since it bypasses Apple's normal review process for apps. Many of us (especially people like me who aren't regular iOS devs and have only anecdotal knowledge of their rules) didn't realize that Apple has an explicit and intentional exception for Javascript run via webview that applies to more than just web pages.

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. "

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)

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.