Question from IETF's Interenet Architecture Board (IAB) web apps, native apps, web-based apps

I asked Hannes Tschofenig (IAB) if there were topics that the IAB and W3C TAG might usefully work on:

"there is one question that I have had several times that also showed up at our most recent IAB technical plenary on Web security. 

 For a long time there was a massive trend towards Web usage driven by the fact that people were more and more reluctant to download applications that run natively on the PC. With the increased usage of tables and smart phones (which use the same operating system) and the excitement of users for download APPs I am wondering where this leaves the W3C as a whole. 

Application developers have (at least) three options for their development: 
* Native code for IOS, Android & co. This typically provides the best performance. 
* Wrapping the code developed for Web applications and use them on the device. 
* Assuming that user's also use the Web browser on their mobile phone."

The question is 
Noah points out that the TAG has touched on these subjects, e.g., this was at least a hallway topic of conversation at the Sophia TAG F2F in April, and the minutes shows a few related discussions on the record, e.g. .

[1] http://www.w3.org/2001/tag/2012/04/02-agenda 
[2] http://www.w3.org/2001/tag/2012/04/03-minutes#item03a


So, I thought I'd send out a note and see if this is a topic other TAG members want to take on, help write up, or at least discuss how we might make progress on writing up. Could we write something about the architectural impact of web apps, native apps, packaged web apps, and its impact on network traffic, extensibility, monetization. What are the tradeoffs?  We might invite Hannes to call in or discuss, or members of webapps working group or ...

Received on Monday, 4 June 2012 20:43:52 UTC