Difference between revisions of "Mobile/Work"

From W3C Wiki
Jump to: navigation, search
(Task Force Deliverables)
Line 11: Line 11:
 
| class="doc0" | [http://www.w3.org/wiki/Mobile/Work#TASK_FORCE:_Documentation_Task_Force Documentation Task Force] || Bringing all documentation together in one dashboard style web application (need Github Link) || Dec 2014 || Early Stages || [https://www.w3.org/Mobile/IG/track/ tracker] || ||
 
| class="doc0" | [http://www.w3.org/wiki/Mobile/Work#TASK_FORCE:_Documentation_Task_Force Documentation Task Force] || Bringing all documentation together in one dashboard style web application (need Github Link) || Dec 2014 || Early Stages || [https://www.w3.org/Mobile/IG/track/ tracker] || ||
 
|-
 
|-
| class="doc0" | [http://www.w3.org/wiki/Mobile/Work#SUB-FORCE:_Closing_the_Gap_.2F_API_Gap Closing the Gap / API Gap] || Continuing work on the Closing the Gap document ([https://github.com/w3c-webmob/gap-analysis Github repo]) || Ongoing Activity || Ongoing Activity || [https://github.com/w3c-webmob/gap-analysis/issues Github issues] || ||
+
| class="doc0" | [http://www.w3.org/wiki/Mobile/Work#SUB-FORCE:_Closing_the_Gap_.2F_API_Gap Closing the Gap / API Gap] || Continuing work on the Closing the Gap document ([https://github.com/w3c-webmob/gap-analysis Github repo]) || Ongoing Activity || Ongoing Activity || [https://github.com/w3c-webmob/gap-analysis/issues Github issues] || Dom ||
 
|-
 
|-
| class="doc0" | [http://www.w3.org/wiki/Mobile/Work#SUB-FORCE:_WebAppState WebAppState] || Continuing the work on the WebAppState Document ([https://github.com/w3c-webmob/mobile-web-app-standards Github repo]) || Ongoing Activity || Ongoing Activity || [https://github.com/w3c-webmob/mobile-web-app-standards/issues Github issues] || ||
+
| class="doc0" | [http://www.w3.org/wiki/Mobile/Work#SUB-FORCE:_WebAppState WebAppState] || Continuing the work on the WebAppState Document ([https://github.com/w3c-webmob/mobile-web-app-standards Github repo]) || Ongoing Activity || Ongoing Activity || [https://github.com/w3c-webmob/mobile-web-app-standards/issues Github issues] || Dom ||
 
|-
 
|-
 
| class="doc0" | [http://www.w3.org/wiki/Mobile/Work#TASK_FORCE:_Offline Offline] || Build sample applications that test ServiceWorker implementations on [https://github.com/w3c-webmob/offline Github] || Apr 2014 || Not started || [https://github.com/w3c-webmob/offline/issues Github Issues] || Natasha Rooney ||
 
| class="doc0" | [http://www.w3.org/wiki/Mobile/Work#TASK_FORCE:_Offline Offline] || Build sample applications that test ServiceWorker implementations on [https://github.com/w3c-webmob/offline Github] || Apr 2014 || Not started || [https://github.com/w3c-webmob/offline/issues Github Issues] || Natasha Rooney ||

Revision as of 08:31, 6 February 2014

Task Force Deliverables

Please see "Task Forces" section below for a description of the Task Forces.

Status of Deliverables
TASK FORCE Deliverables Timetable Target Status
(Jan)
Tracker Contact Notes
Use case and requirements for network information Document use cases for Network Information API based on what native apps are doing. June 2014 Early Stages Github issues Marcos Caceres
Documentation Task Force Bringing all documentation together in one dashboard style web application (need Github Link) Dec 2014 Early Stages tracker
Closing the Gap / API Gap Continuing work on the Closing the Gap document (Github repo) Ongoing Activity Ongoing Activity Github issues Dom
WebAppState Continuing the work on the WebAppState Document (Github repo) Ongoing Activity Ongoing Activity Github issues Dom
Offline Build sample applications that test ServiceWorker implementations on Github Apr 2014 Not started Github Issues Natasha Rooney
Scrolling - On Hold tracker
Homescreen Bookmarking / Installable Webapps Use Cases and Requirements for Installable Webapps Doc Dec 2013 Early Stages Github Issues List Marcos Caceres
Mobile Web Best Practices Updating the Mobile Web Best Practices document Github Apr 2014 Early Stages Github Issues Natasha Rooney
Payments Document Use Cases and Requirements Github Mar 2014 Early Stages Github Issues Natasha
Permissions Documenting current issues with permissions and defining the questions which need to be asked to find a better model. Github Repo Early Stages Github Issues TBD (Dom covering atm)
Developer Tools / Diagnostics / Debug tracker

Task Forces

The Web and Mobile Interest Group manages it's work via task forces. Members add themselves to a task force and then work collaboratively via the public mailing list and github to complete the work. Below is a list of our task forces. The table above reflects the work they are doing and the stages it is at.

TASK FORCE: Documentation Task Force

LEADER:

PARTICIPANTS:

GITHUB LINK:

LINK: Web App State, Coremob Report

GOAL: Pull in all helpful documentation into a more automated, dashboard style of data representation. Should cover: use cases, requirements, Closing the Gap and Web App State.

TASKS

  • Sort through Marcos's Github issues on Coremob
  • Find a new section for requirements / use cases



SUB-FORCE: Closing the Gap / API Gap

LEADER:

PARTICIPANTS:

GITHUB LINK: https://github.com/w3c-webmob/coremob-report, Gap Analysis Discussion, Spec Review Checklist

LINK:

GOAL: The Closing the Gap report focuses on Dom has already done some great work for us here, and we want this to continue.

TASKS:

  • Add to the "App Types" table
  • Add horizontal aspects such as 'accessibility'
  • Add statistics and figures from Vision Mobile report and PhoneGap Analysis which Dan Appelquist reported at the TPAC meeting (showing importance of some APIs such as Network Info, Camera etc.)
  • Check content and update where necessary (perhaps start by raising issues in Github and then go through issues and solve)
  • Long term goal: add to new dashboard style documentation



SUB-FORCE: WebAppState

LEADER: Dominique

PARTICIPANTS:

LINK: http://www.w3.org/Mobile/mobile-web-app-state/

GITHUB LINK:

GOAL: This document summarizes the various technologies developed in W3C that increase the capabilities of Web applications, and how they apply more specifically to the mobile context. This includes such technologies as Graphics, Multimedia, Device Adaptation, Forms, User interactions, Data storage, Personal Information Management, Sensors and hardware integration, Network, Communication_and_Discovery, Packaging and Performance & Optimization. For each section there is an explanation of the technology and a table representing the state of the standard, mobile browser implementations, links to test suites and developer documentation. Dom has done some great work on this and we are keen for this to continue. It is also worth noting that Dom has begun work on automating a lot of this information, and we would like to continue to investigate implementation of as much of this information as possible. Currently some of the data is automated, and some is manual. 'caniuse.com' is a source of some of the data.

TASKS:

  • Dom is creating JSON files for this data, investigate how we can help him so this

Want to allow more groups to use this

  • Check content and update where necessary (perhaps start by raising issues in Github and then go through issues and solve)
  • Investigate automation
  • Long term goal: add to new dashboard style documentation



TASK FORCE: Offline

LEADER: Natasha Rooney

PARTICIPANTS: Marcos

LINK: Original Discussion, Storage Quota Discussion

GITHUB LINK: ServiceWorker, Github Link

GOAL: The new ServiceWorker will allow web apps to have offline capabilities by allowing developers to create 'caches' and controlling their behaviour. Once an implementation of ServiceWorker is available this task force should assist the Web Apps WG in providing demo apps and tests for the use cases around offline web apps (with an emphasis on mobile devices and mobile user agents).

TASKS

  • Read Use Cases from ServiceWorker docs
  • Start building tests based on these use cases
  • Keep up-to-date on implementations

TASK FORCE: Scrolling

LEADER:

PARTICIPANTS: Stakagi

LINK: Original Discussion, 60fps scrolling using pointer-events: none, CSS Ninja

GITHUB LINK:

GOAL: At our TPAC meeting we talked about trends within scrolling such as "Infinite Scrolling", "Momentum scrolling", and whether there a need for better / configurable garbage collection. We recognised the issues with scrolling, and noted we need to analyse the situation to both [1] help us find out what we can do next to help the situation and [2] assist other WGs and implementers discover the issues we are facing.

TASKS

  • Analyse the issues (investigate what is causing the "jank"(means Poor Quality?), gather the articles and organise the issues) and create a report similar to the "Installable Webapps" document.
  • Investigate related existing standardization works.

SEE ALSO http://jankfree.org/


TASK FORCE: Homescreen Bookmarking / Installable Webapps

LEADER: Marcos

PARTICIPANTS: Ernesto, Anssi, lots of people in #manifest

LINK: Original Discussion, Supporting Research - Ernesto Jimenez

GITHUB LINK: https://github.com/w3c-webmob/installable-webapps

GOOGLE DOC LINKS: List of Apps and Device Orientation

GOAL: Provide an overview of how web applications have started to be integrated into native application environments, and outline the use cases and requirements for a standard that could allow users to "install" web applications.

TASKS

  • Continue working on the document (hosted on Github)
  • Need to pull in details from FFOS and Chrome Beta

TASK FORCE: Mobile Web Best Practices Guide

LEADER: Natasha

PARTICIPANTS: Tobie, Jo, Terence Eden

GITHUB LINK: https://github.com/w3c-webmob/mobile_best_practices

GOAL: Update the Mobile Best Practices Guide. Define a future for the document and whether it should contribute or be contributed to by other sources on the web.

TASKS

  • Continue posting issues on Github (any issues with the original document)
  • Fork and submit pull requests for new additions to the document / changes to the document
  • Define a future for the document (discuss via mailing list)

TASK FORCE: Payments

LEADER:

PARTICIPANTS: Ernesto?

LINK: Original Discussion, Web Payments CG

GITHUB LINK:

GOAL: Within payments there are many aspects to cover; these are all being considered by the Web Payments CG. This Web Payments CG requested that we provide them with some use cases and requirements which have an emphasis on mobile. The key focus here is likely to be "input fields". In a use cases and requirements document we should clearly state what issues exists and what could be done better. Participants can use native user experiences (Android and iOS) to compare.

TASKS:

  • Document use cases for web payments
  • Document requirements for web payments
  • Document issues around user experience for mobile web payments
  • Document how things can be made better
  • Compare with native payment methods



TASK FORCE: Permissions

LEADER:

PARTICIPANTS: Dom,

LINK: Original Discussion Dom's permission's presentation for the TAG

GITHUB LINK: Web Permissions Requirements (Dom)

GOAL: Permissions model for web apps is different then for native apps. We should start to document the differences, analyse the current situation, and comment on what needs to happen to allow mobile web apps to utilise a defined permissions model. To begin, the permissions topic must be brought up with the TAG so we make sure we are aligned with W3C goals in this area.

TASKS:

  • Discuss the permissions topic with the TAG and share findings (Dom)
  • Start the analysis doc include: current situation, differences with native, how we see the future of web apps to be
  • Request help from experts in the field (Boris Smus, Rich Tibbet)



TASK FORCE: Developer Tools / Diagnostics / Debug

LEADER:

PARTICIPANTS:

LINK: Developer Tools Discussion, Debug Discussion, Vision Mobile: What we are missing is Tools

WIKI LINK: Dev Tools Wiki Page

GOAL: Investigate current developer tool offering and see if there is anything missing. Consider new tools such as Web Driver and APIs such as the Diagnostics API and Console API.

TASKS:

  • Investigate tools and add to wiki page (Dev Tools Wiki Page)
  • Recruit dev tools experts to the Web and Mobile IG (Angelina Fabbro and some of the people in her team from Mozilla, Paul Irish, Paul Lewis)
  • Document missing tools and start working on use cases for these



TASK FORCE: The Force

GOAL:This is the task force that runs the rest of the task forces. They also manage any developer outreach or education that the group may complete.

MEMBERS: Natasha Rooney, Marcos Caceres