FlexApp One Software Requirements
The FlexApp One software zip file contains the following:
- FlexApp One ReadMe Files
- FlexApp One Bundler—Bundles traditional FlexApp packages into distributable executables.
- FlexApp Run-time Service Installer—Installs prerequisite service on end user device to run FlexApp One Applications. Refer to the Prerequisites to Run FlexApp One Applications section below.
Additionally, the FlexApp Packaging Console Installer is available for download to create traditional FlexApp packages as well as FlexApp One packages. For more information, refer to the FlexApp Packaging Console Guide.
FlexApp One Bundler
The FlexApp One bundler requires the following for operation:
| Component | Requirements |
|---|---|
| OS Platforms Supported | Windows 10/11 or Windows Server 2016/2019/2022/2025. Only 64-bit versions are supported. Both physical and virtual instances are also supported. |
| CPU | 2 CPUs minimum |
| Memory | 4 GB minimum |
| Storage Space | Enough storage to hold the resulting FlexApp One executable. The resulting FlexApp One application will be approximately 25-50% smaller than the initial FlexApp package. |
FlexApp One Applications
The FlexApp One service engine is required to run FlexApp One applications on end user devices. The FlexApp One end-user machines require the following:
| Component | Requirements |
|---|---|
| OS Platforms Supported | Windows 10/11 or Windows Server 2016/2019/2022/2025. Only 64-bit versions are supported. Both physical and virtual instances are also supported. |
| CPU | 4 CPUs minimum |
| Memory | 6 GB minimum |
| Storage Space | Enough storage to hold each used application, SSD preferred. |
Prerequisites to Run FlexApp One Applications
To run FlexApp One applications, the FlexApp run-time service must be installed on the end user’s machine. The run-time service can be included in the base image or installed one time from a FlexApp One application. The FlexApp One bundler will include the necessary files in the resulting EXE.
To install the run-time service from a FlexApp One application:
(This requires privilege elevation.)
- Run any FlexApp One EXE to install the FlexApp service and engine.
- OR
- Run the Installer.exe using the
--installcommand line argument. Installer.exe --install
Well-Managed Devices
FlexApp One is designed to play back applications in a user’s environment from a self-contained executable. These applications run as if they are natively installed in the user’s Windows environment without modifying the base image. Windows system files and the Registry remain unchanged, keeping the base image clean, unlike what would happen when a traditional application is installed or uninstalled. Having a clean, well-managed device provides a repeatable, consistent playback for each FlexApp One application. However, in order to maintain that experience, these end user devices need to start out as clean, well-managed devices. Playback of FlexApp One executables on devices that have been modified with the addition of other software might give unexpected results. The following are recommended:
- End-user devices should have a base image installed without additional applications.
- End-users should not be allowed to install non-managed software.
- Packaging and bundling of software should follow packaging best practices and occur on virtual machines that can be rolled back to a clean state after each run.
