Skip to content

Distribution methods

Shared installer

For Free Developer and Business users, we use the following approach:

  • We provide self-extracting installer, that ships the engine as a separate product. Multiple apps on the same system can use one shared engine.
  • If the engine is already present, the installer checks the version and upgrades it if needed. Upgrades are backwards compatible and won't break other apps using the engine.
  • The engine can only be fully uninstalled after all apps that depend on it are removed.

Example

Your app is installed in C:\Program Files\YourApp. During installation, it installs or upgrades the engine in C:\Program files\ViveEngine.

Custom build

For Business users, we also support an alternative approach:

  • We create a custom edition of the engine for the customer, with separate identifiers and certificates.
  • This edition is separate from all others and can safely coexist with any other ViveEngine installations.
  • We provide a bundle that can be shipped as part of your app, rather than as a separate product.

Example

Your app is installed in C:\Program Files\YourApp. During installation, it sets up the engine in C:\Program Files\YourApp\EngineBundle.

Custom builds are more self-contained and often preferred by larger customers who want strict control over their runtime environment.

White label

White-label solutions always use the custom build approach:

  • A custom edition of the engine is embedded directly into the app.
  • The app fully controls the engine version and update cycle.
  • End users do not interact with a separate “engine” installer.