As is typical, the blog post correctly identifies issues with iOS and Safari, but in many cases presents misleading, inflammatory, or just plain incorrect information.<p>Here are some things that are correct:<p>1. Apple would prefer that you write native apps.<p>2. WebKit on iOS is missing many features that natives apps have.<p>3. Allowing third-party rendering engines is not a security vulnerability, contrary to Apple's claims. In many cases it actually <i>improves</i> security for users.<p>4. Apple's rhetoric around anything to do with the App Store is generally self-contradictory and embarrassing.<p>Here's what's wrong:<p>1. Apple underinvests in their browser: they most decidedly do not. They do choose to work on things they want to work on, but WebKit is not lacking on engineering talent.<p>2. "Native apps" are somehow ambiguous and hard to define: they are not, it's been pretty clear that you are using the blessed OS framework and language to create them. The only confusion has been from people wrapping up various shims in minimal native glue and calling it "native", sowing confusion.<p>3. Apple's choices in what to implement are done without regards to user experience: it's fairly clear that this is not true. The web platform has shown that poorly thought out features come back to be privacy nightmares, and it is important to consider additions before including them in a browser. There are features that could ostensibly be added in a way that helps resolve these concerns, but it is not fair to discuss them as being trivial to implement or privacy posturing–even if they happen to benefit the native app ecosystem.<p>The rest of the piece is much of the same with cherry-picked links and thinly-veiled agenda, so I'm not going to spend too much time going over all of it, but I think it's pretty obvious that Alex Russell has a pretty clear position he wants to push (get native APIs into web apps on iOS) because of his current employment (Project Fugu for Chrome). He correctly identifies many failures in the iOS web ecosystem but in the pursuit of pushing his point fails to address multiple major issues, including actual privacy concerns in the APIs he pushes and the internal contradiction of "the web is safe and sandboxed, so let's put a bunch more API surface in it to make it like native apps, which are security nightmares". It's a nuanced issue and this post lacks much.