- From: Maffett, Ian <ian.maffett@intel.com>
- Date: Sun, 18 May 2014 01:04:58 +0000
- To: Dominique Hazael-Massieux <dom@w3.org>, "public-web-mobile@w3.org" <public-web-mobile@w3.org>
This looks great! Iıll try to take a pass through them next week and add any more. For telephony - Phonegap *should* offer the same support of the browser platform for the selected OS. I know there were a few bugs that theyıve fixed with tel: protocol handler not being launched properly, but there are noted workarounds. On 5/16/14, 3:56 PM, "Dominique Hazael-Massieux" <dom@w3.org> wrote: >Hi, > >A while ago, I started to survey what APIs mobile platforms expose, in >native ecosystems (iOS, android, Windows) and in Web-based ones >(FirefoxOS, Chrome Apps, Tizen, PhoneGap). > >While I'm not quite done, I thought I would already share what I have >(also in the hope that others might want to contribute to it too): >https://github.com/w3c-webmob/web-api-gap/tree/master/features > >My goal with this survey is to more easily find APIs that we could get >inspiration from, as well as to identify APIs that ought to be low >hanging fruits for the Web (e.g. are present in most Web-based >platforms, but not in the browser). > >For instance, I have generated the attached view that shows which APIs >are available in browsers (or least have an available spec), which have >a draft in sysapps-space, and which have an equivalent in one of the >Web-based systems. > >(the way this is currently shown is probably not the clearest; hopefully >people can already make sense out of it, and help improve it) > >I'll keep working on this on and off; I would appreciate feedback, and >contributions even more so :) > >Thanks, > >Dom
Received on Sunday, 18 May 2014 01:05:27 UTC