[yggydrasily]

The article only gives three examples of APIs that are "missing" on iOS, and one of them is the vibration API.

Since when is the vibration API a "good example" of something necessary to "give the full app experience on mobile" (using the article's language)? Other than message & phone call notifications, I don't want apps vibrating my phone all the time. The W3C page they link to describes it as a "form of tactile feedback", but that's nonsense, unless they are talking about the touch feedback that newer devices like the Apple Watch provide, which is done mostly at the system level.

Another example the article gives is CSS touch manipulation, which Apple has already started working on[0]. So, the article is 1 for 3.

[0] https://bugs.webkit.org/show_bug.cgi?id=149854

[Silhouette]

There are much more serious omissions if you're trying to build a web app that works with Apple devices. For example, despite all the protestations about how necessary it was to kill off Flash and use HTML5 for playing multimedia content instead because Plugins Are Evil(TM), it is actually a plugin rather than Safari that is playing a video when you visit a site on an iPhone or iPad. As soon as you want to do anything interesting with all the extra power that making audio and video just two more types of content on the Web should bring... even basic stuff just doesn't work. Except for every major device but Apple ones, that is.

[Touche]

A more important API than Vibration is the Web App Manifest which is the new way to do "Add to Homescreen": http://www.w3.org/TR/appmanifest/ Pretty sure WebKit doesn't support this yet.