The EXO UI and EXOengine are designed to use the standards that help your business run.

Supported Application Formats
     
  • HTML and HTML5 based applications
  • Native EXOscript Applications
  • Flash based applications (independent runtime required)
  • Silverlight based applications (independent runtime required)
  • JAVA based applications (independent runtime required)
  • Binary Applications (OS dependent)

HTML Apps

Direct, easy access of client-side features via the EXOengine.

  • Local data storage
  • Access to file system
  • EXO UI information and control
  • System information and control
  • Multi-touch support
  • Sensors
  • RS232
  • Flash, Javascript, and Silverlight when their third-party runtimes are installed.

Binary Apps Integration

Binary apps can be distributed through the EXOstore and/or launched from the EXO UI.

The EXO UI supports different ways to run binary apps:

  • Independent binary
  • Embedded binary
  • HTML UI with binary as a service

Integration of any Windows compatible binary is possible.

Independent Binary Apps

Clean integration in EXO UI

  • Displayed in the EXO UI application area (control zones still available)
  • Integration in the EXO UI multi-tasks feature
  • Support of EXOkeyboard

Binary applications can be distributed via the EXOstore

  • Original installation procedure or one click installation
  • Shortcut to be launched from the UI

Embedded Binary

A binary can be embedded in an EXOapp (ex. ActiveX ) in order to establish
a direct communication between the EXO UI andthe binary code.

In-deep communication between the EXO UI and the embedded binary

  • Capable of high-frequency and intensive data exchange
  • Act as a service (hidden) or provides the UI (control the output)

Portability

  • Embedded binary can be part of the EXOfile
  • Possible EXE output format (no need of the EXO UI or a runtime to run it)

HTML UI with binary as a service

EXOPC provides a structured, light method to convert a non-touch friendly application (including legacy apps) into a touch friendly application.
The existing non-touch binary application is used as a service (running hidden) and interacts with a dedicated HTML UI running in the EXO UI or deployed as an autonomous application file.

Keep the exact same binary file

  • No re-writing
  • Create an independent HTML UI
  • EXOengine to communicate between your HTML UI and  your binary

Add a “local server mode” support

  • Your application is made invisible
  • Add the code to reply to the queries sent by the HTML UI
    (Windows message, local file system, window title, plus other possible methods)

EXOengine versus Web Service

EXOengine

  • No latency
  • Rich UI
  • Secure (offline support)
  • Auto-update feature

Web Service

  • Latency, slow, can be down
  • Expensive to secure
  • Light UI for bandwidth consideration

EXOengine vs. Web Service

.EXO or .EXE files = Flexibility for the ISVs

Depending on your needs, you can create .EXO or .EXE files to distribute your application.
Both formats will allow you to include an HTML UI and binary files or dependencies.
ISV Flexibility