Skip to content

The Cameo Project vs. Alternatives

msrichmond edited this page May 16, 2013 · 2 revisions

The Cameo Project vs. runtimes for other languages.

The Cameo application runtime is based on W3C standards: HTML5, CSS and JavaScript. Unlike the languages supported by earlier runtimes, W3C standards are implemented in multiple forms, by multiple companies and in open source as well as commercial implementations. A broad range of open source as well as commercial tools and projects support the developer. When you use a Cameo application runtime, you are participating in a growing ecosystem.

The Cameo Project vs. a browser.

Browsers do a great job of supporting W3C standards, but they are not allowed to support the APIs from the Systems Applications Working Group. This is because these APIs access platform features which if known to a web site and combined with other data known to the browser would allow violations of the consumer's privacy. In addition, browsers impose an extra level of indirection when launching an application, namely, launching the browser before a consumer can launch the application. With the Cameo Application Runtime, a consumer launches the application directly.

The Cameo Project vs. other HTML5 runtimes.

The Cameo Project supports all three distribution models (managed, embedded, bootstrapped) on multiple operating systems (see roadmap). Support is planned for SysApp APIs. Support is planned for Tizen Web Apps APIs. Extra support is included for applications aimed at mobile devices, e.g., orientation lock and viewport interaction.

A platform owner who provides a Cameo managed runtime can control runtime updates for a suite of applications without having to embed the runtime in each one. The project includes a deployable server infrastructure for managing updates. A platform owner may include API’s that are unique to their platform's applications.

An application developer who uses the Cameo Embedded Runtime gets an easy-to-use Web View where multi process is transparent for the application. A developer can override native integration, e.g.,. select item selector, context menus, which can be useful for new deployment platforms such as automobile, televisions, etc.

An application developer who uses the Cameo Bootstrapped Runtime creates a package/binary for the targeted OS from their source code allowing installation of the runtime on the client’s machine if not present.

Introduction

Clone this wiki locally