Difference between revisions of "Web App"

From MgmtWiki
Jump to: navigation, search
(Created page with "==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 o...")
 
(Solutions)
Line 12: Line 12:
  
 
==Solutions==
 
==Solutions==
*Certification of the [[Web App]] please refer to page [[Web Manifest]].
+
*Certification of the [[Web App]] please refer to page [[Web App Manifest]].
 
 
  
 
==References==
 
==References==

Revision as of 20:25, 8 May 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.
  • 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

References

  1. Native App Security page in this wiki
  2. Native App Privacy page in this wiki
  3. Native App URI Handlers page in this wiki
  4. W3C page on web apps best practices as of (2010-12-10).
  5. IETF RFC 8252 OAuth 2.0 for Native Apps https://tools.ietf.org/html/bcp212#section-7.2
  6. Apple App Store Review Guidelines https://developer.apple.com/app-store/review/guidelines/