Skip to toolbar

Community & Business Groups

Merging of Web and Mobile APP Community Group

The mission of this community is to be an incubator of optimizing Web technology for the merging of Web and mobile APP, and to develop related requirements and approaches.

Group's public email, repo and wiki activity over time

Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.

No Reports Yet Published

Learn more about publishing.

Chairs, when logged in, may publish draft and final reports. Please see report requirements.

This group does not have a Chair and thus cannot publish new reports. Learn how to choose a Chair.

Call for participation: Online meeting on Gesture Events Standard in Web

Hello All:

We will organize an online meeting to discuss the proposal of Gesture Events in Web. Please provide your feedback of your available time on doodle:

(If you have any questions, please contact: )

Introduction of native app gesture and Gesture Events in web

Smartphone OS normally have Touch and Gesture as a way to interact with users.

Touch function is used to capture the information of touch events (e.g. the position of the touch point etc.)happening on the screen.

Gesture function is used to specify users’ more complex interactive operation with screen, such as pinching, rotating, swiping, double-tapping and so on.

Although Touch is supported by many platforms and the touch events model has been defined in the W3C Touch Events specification [1], Gesture are not widely supported currently.

Nowadays, gesture events are widely used in web. However, web developers can only use Touch Events to implement gesture functionalities. They may have to develop multiple versions of gesture events in order to adapt different browsers due to the lack of gesture events standard in web. Thus, web developers always choose to implement the gesture events by importing external toolkits when they start a new web project. The development effort of gesture functions for every single browser and learning cost for different API and parameters of toolkits result in low efficiency.

To solve this issue, we propose to define a Gesture Events standard in W3C, the benefits are:

  • Web developers can follow this Gesture Events standard, and deal with gesture events more efficiently without any additional effort for every single browser.
  • Developers do not need to learn different API and parameters of gesture functions’ toolkits.
  • Users can interact with mobile web apps more smoothly when using the built-in gesture events.

Gesture Events list and use cases

Events list:

Use cases: