Re: Cordova/W3C


I understand what you're asking but I'm not sure if that is something that 
the Cordova team is capable of helping with.  We don't know how end users 
are using each of the Cordova APIs and there really isn't a good way to 
ask them.  Cordova is installed using npm ( and the plugin repositories have 
publically visible download stats ( We 
do not have access to contact information for individual developers let 
alone the code they have written.  There is the Google Group for Phonegap 
as well as the list of developers (opt-in by the developers themselves) as 
well as the Cordova blog where we could submit a poll.  But the responses 
are unlikely to reach a good subset of users.  There are some case studies 
and featured applications from the Phonegap team ( 


Lisa Seacat DeLuca
Mobile Engineer | t: +415.787.4589 | | | | | | 

From:   Marcos Caceres <>
To:     Lisa Seacat DeLuca/San Francisco/IBM@IBMUS
Cc:     Dominique Hazael-Massieux <>, DAP 
Date:   02/27/2014 06:12 PM
Subject:        Re: Cordova/W3C

Hi Lisa, 

On Thursday, February 27, 2014 at 7:34 PM, Lisa Seacat DeLuca wrote:

> During today's DAP Working Group call, we chatted about pushing the 
alignment between the Apache Cordova APIs and the w3c specs. I'm sending 
out this email to get the ball rolling and start discussing some ideas to 
make this happen. 

What we *really* need from the Cordova side is pointers to *real 
applications* (i.e., those made by independent developers) that show us 
how real developers are using the APIs. We can't align on anything until 
we see why and how actual people are using the APIs. Otherwise, we are 
just blindly speculating on theoretical use cases. 

Cordova has the most experience and potentially the most data on the usage 
of these APIs. I cannot think of any way to better inform the 
standardization process than by allowing us to examine the code of 
applications built with Cordova to see what and how developers are using 
these APIs. This would be in alignment with the Extensible Web Manifesto 
[1], which states:

"We aim to tighten the feedback loop between the editors of web standards 
and web developers.... We prefer to enable feature development and 
iteration in JavaScript, followed by implementation in browsers and 

I just can't emphasize the above enough.  Ultimately, we should end up 
with a bunch of documents that look like the netinfo one:

Kind regards,

Received on Friday, 28 February 2014 15:35:40 UTC