[German]In Windows 10 Version 2004, Microsoft will introduce so-called Hosted Apps in the Windows App Model. Here is some information about what Microsoft understands by this new app model.
Apps for Windows 10 are be delivered via signed MSIX packages. A package provides the identity so that it is known to the system and contains all files, assets, and registry information for the application it contains.
Many apps have scenarios where they want to host content and binaries from other apps. There are also scenarios where the host app is more like a runtime engine that loads script content. In addition, there is a desire for these hosted applications to look and behave like a separate application on the system, with their own startup tile, identity, and deep integration with Windows features such as background tasks, notifications, and sharing.
With the Hosted App Model, a retail kiosk application can be easily renamed, or a Python or Powershell script can now be treated as a separate application. Hosted apps are registered as independent apps on Windows, but require a host process to run. An example would be a script file that requires the host (such as Powershell or Python) to be installed. In itself it is just a file and has no way to appear as an application on Windows.
With the Hosted App Model, an app can declare itself as a host. Then packages can declare a dependency on that host and are called hosted applications. When the hosted app starts, the host executable is then launched with the identity of the hosted app package instead of its own identity. This allows the host to access the contents of the hosted app package, and when calling APIs, it does so using the identity of the hosted application.
The concept was presented a few days ago in the Windows blog. There you can read the details. The concept of hosted apps is only of interest to app developers – end users are unlikely to notice anything, except when a hosted app doesn’t work because the host can’t be contacted. (via)