Difference between revisions of "Web App"

Revision as of 11:34, 16 August 2019

Full Title or Meme

A digital User Experience that is operating on a User Device and is typically supplied by the Web Site.

Context

• As the functionality of the Web Browsers and HTML 5 becomes ever more capable, a Web Site can generate a Web App entirely within the browser.
• There is no real demarcation between a Web Site and a Web App except for the existence of a Web App Manifest.
• Typically the Native App will run on a User Device in the user's physical possession, but it is possible that the agent is running on a service in The Cloud.
• The Native App may act like a browser and supply an HTTP user agent string, but it should not be considered to be a User Agent.
• The Native App may act like a web server by registering Native App URI Handlers so that it will receive registered URLs entered into the browser.

Problems

• The user will be hard pressed to distinguish between a Web App and a Native App which is a problem as the operating of the environment of the Web App is constrained by the browser that is selected by the user, while the Native App can ask for access to device capabilities that are not available to the Web App.

Solutions

• Certification of the Web App please refer to page Web App Manifest.

References

Internal Material

1. Native App Security page in this wiki
2. Native App Privacy page in this wiki
3. W3C page on web apps best practices as of (2010-12-10).
4. Progressive Web App page in this wiki

External Material

1. Web APIs When writing code for the Web, there are a great many Web APIs available. The link contains a list of all the APIs and interfaces (object types) that you may be able to use while developing your Web app or site. Web APIs are typically used with JavaScript, although this doesn't always have to be the case.]