Smarter Web Apps

31 Oct 2012


See also: IRC log


Arnaud_Braud, Tomoyuki_Shimizu, Dave_Raggett, Jonathan_Jeon, Wonsuk_Lee
Brian Sullivan


<Arnaud> Topic : Smarter Webapps for Smarter Phones

<Arnaud> RRSAgent please make minutes

<scribe> scribe: dsr

Brian talks through the proposed agenda

Bryan references the GSMA's Smarter Apps guidelines and points to Kamran Kordi who was heavily involved in their preparation.

The guidelines cover good practices, performance and efficiency.

What can you do today with the current web platform, and what can we expect tomorrow?

See http://www.w3.org/wiki/TPAC2012/smarterwebapps

Bryan talks through: http://www.w3.org/wiki/TPAC2012/smarterwebapps#What_you_can_do_today:_efficiency_focus

Need guides for server implementation and comparative performance of HTTP polling and web sockets.

Apps with continuous connections consume resources and need to add value in compensation.

Sharing a connection is better than opening many connections. This suggests using cooperative request scheduling.

Bryan shows Hidetoshi Yokota's slides on network aware web apps.

toshi: enabling web apps to choose the best network interface available for a given task.

<JonathanJ1> http://www.w3.org/wiki/TPAC2012/SessionIdeas#Smarter_Webapps_for_Smarter_Phones

<JonathanJ1> http://www.w3.org/wiki/TPAC2012/smarterwebapps

<tomoyuki> Toshi could you upload the ppt file to Wiki?

Bryan demo's the network information API test

This involves navigator.connection events

<gmandyam> +q

what more should w3c do as next steps? http://www.w3.org/wiki/TPAC2012/smarterwebapps#What_Should_W3C_Do_as_Next_Steps

gmandyam: Bryan, you didn't mention anything about keepalive, which has implications for battery life.

Bryan: it was mentioned that web sockets doesn't require keep alive.

gmandyam: there is the danger that developers will add their own keep alive messages on web sockets with negative consequences.

there is a connection manager running in the OS that ultimately takes decisions, it is up to the web app however, to make reasonable requests.

raman: why would I want a web app to change how connection management is working on my device?

Bryan: the app could prefer the wifi network when appropriate

raman: this is a symptom that we have failed to stitch the os and web platforms together properly.

Bryan: the problem is that the OS doesn't know the application context.

raman: are you talking about starting/stopping a network interface?

Bryan: no, only about app awareness.

toshi: the application should be able to make requests of the OS network interface manager.

raman: I totally buy the value of network state awareness.
... if apps are clamoring to use given network interfaces, we can run into a mess.

David Rogers: the browser should be aware of the user's device level preferences.

Bryan: we need to clarify the level of requests that the app can make to the OS connection manager.

??: I believe that the OS is in a much better position to make decisions, and that there are privacy risks if we allow the apps to become involved?

some discussion on video streaming - is adaptation after the fact - or can we pass preferences in advance?

LTE might be preferable to WiFi, which could be metered.

<JonathanJ1> Do we need consider to openCM API like API on the web ? - http://bit.ly/TupGCf

<sburr> +1 to a more semantic representation of network-related information being exposed to web layer

Bryan: making the app aware, allows it to indicate its preferences in context

Providing preferences with the network request seems worth considering.

The preference could include a request to kill the connection if the device is roaming (high billing cost)

?? (from Apple) want to see discussion of privacy implications.

Raman: the roaming decision should be made by the user not the app

The connection manager needs to resolve conflicts between policy, user and web apps.

toshi: 3GPP puts the operator policy higher than the user's

Bryan: we are out of time, I will update the wiki page based on what we've heard.

please feel free to join the community group and contribute further!

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.137 (CVS log)
$Date: 2012/10/31 16:00:41 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.137  of Date: 2012/09/20 20:19:01  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: dsr
Inferring ScribeNick: dsr
Present: Arnaud_Braud Tomoyuki_Shimizu Dave_Raggett Jonathan_Jeon Wonsuk_Lee
Agenda: http://www.w3.org/wiki/TPAC2012/SessionIdeas#Smarter_Webapps_for_Smarter_Phones
Got date from IRC log name: 31 Oct 2012
Guessing minutes URL: http://www.w3.org/2012/10/31-smarterwebapps-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report

[End of scribe.perl diagnostic output]