Abstract: Techniques for integrating always-on software applications are provided. A simulator for the software user interface interfaces with the always-on software application. The simulator operates similar to the software user interface, except that it does not affect the hardware user interface (e.g., the screen display). For example, the simulator user interface can execute a state machine that is the same as the software user interface. In this manner, the always-on software application drives the simulator software user interface when it is not in the foreground, which allows the simulator software user interface to direct the hardware user interface when the always-on application executes in the foreground.

Abstract: Techniques for remotely building and managing software applications are provided. Computer code of the principal developer (e.g., source code, object code or libraries) that is not to be shared with external parties is stored on a restricted internal server while computer code of a third party supplier or customer is stored on a shared server by the supplier. A daemon executes on the restricted server to access the computer code on the shared server, download the computer code to the restricted server and call the internal compiler, linker, etc. to build the complete software application. The build is then stored or uploaded on the shared server (by the daemon) for the supplier or customer to access. Files related to the build that are desirable not to share (e.g., map files and all sensitive source code files) can be stored on the restricted server.