Community & Business Groups

Web App Source Code Protection Community Group

The goal of this community group is to explore solutions for protecting web app source codes. It is well-known that web page source codes are visible to the public due to the openness of the Internet and the W3C standards. With the advent of HTML5, the web apps become popular, especially the mobile web apps. Web apps can be classified as either Hosted App or Packaged App. The source code of Packaged Apps (such as the apps in Firefox OS or Tizen OS) are installed and running locally. Users can easily view the source code. Similarly front end source code of Hosted App can also be easily seen by anyone. In this case, the publicity of source codes becomes a problem. Because web developers never hope their web apps are easily copied by others. Therefore, this group intends to find mechanisms of code protection for web apps, especially for packaged apps, making the source codes (e.g. HTML, CSS, JavaScript), as well as relevant resource files (image, audio and video, etc.) cannot be seen easily. Thus, the interests of web developers will be protected.

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.

Publish Reports

Web App Source Code Protection CG is trending in Social Media

As part of my work in the W3C Communications Team, I monitor the social media and the press for W3C technology and stories. The Web App Source Code Protection Community Group has been much written about in the past few weeks.

See for example this Topsy graph. It shows the number of tweets per day that mentioned “Web App Source Code Protection Community Group”:

Screen Shot of topsy analytics for Web App Source Code Protection Community Group
Screen Shot of topsy analytics for "Web App Source Code Protection Community Group"

A more remarkable example is this Topsy search for tweets that mentioned the URI of this group‘s homepage:

Screen Shot of topsy search result numbers for the URI of the Web App Source Code Protection Community Group
Screen Shot of topsy search result numbers for the URI of the Web App Source Code Protection Community Group

The sentiments people share are that of worry and concerns, to say the least.

Another part of my work is to help run —and assess— the W3C Community Groups operations. Community Groups are run by the community and hosted by W3C. They do not necessarily represent the views of the W3C Membership or staff, and this is a clarification that we can not emphasise enough.

I gave a quick look at the number of blog posts of this Community Group, the traffic in its mailing list archives and its (unused) wiki (both linked from the side menu), and the contrast with the trend in social media is striking.

The proposed work may get traction, or not, this is entirely up to this community group with 39 participants, many of whom, I suspect, are observers.