Some require advanced programming skills, whilst others are aimed at end users. However, it should provide a broad picture of the approaches that have been taken in respect to handing trust and permissions, and potential ways to move towards a general consensus on how to extend the Open Web Platform.ĭeveloper tools range widely in their sophistication. This whitepaper surveys the field, but does not claim to be fully comprehensive. for the associated manifests, and the use of proprietary APIs. There is a lack of interoperability for packaged apps due variations across platforms, e.g. Web applications can also be packaged for local installation, akin to native applications. Web applications are traditionally hosted by HTTP servers, with the various resources making up the application being loaded dynamically by the web run-time (i.e. Hybrid approaches have emerged which allow developers to use standard web technologies together with proprietary extensions, and then compile to the native app platform. A performance and capability gap has emerged between native and Web apps. This has been very successful on mobile devices, where developers have been able to take advantage of vendor support for a comprehensive range of APIs. However, the success of the Web has encouraged proprietary platform owners to support native applications and app stores. For developers seeking to reach a wide range of devices and operating systems, the Web is the obvious choice. desktop, smart phones, tablets, TVs and cars). It is the only vendor neutral platform that spans such a wide range of devices (e.g. The Open Web Platform is based upon open standards and is supported on billions of devices.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |