Unity OS and Hardware Requirements

Written By Sam Walton (Super Administrator)

Updated at May 16th, 2025

TLS-1.2 or higher encryption cypher is required for all connectivity with the IBSS platform. Older insecure encryption ciphers are now disabled by Microsoft, hence, very old or unsupported devices will be unable to connect. Any browser and OS used on your active devices must meet this minimum requirement.

The IBSS platform supports the following Mobile OS for Unity together with the following specifications.

Android supported versions

Supported Versions
Minimum Recommended Hardware
Unity is supported on
devices running Android 5 or higher
  • CPU: 64-bit Quad-core A73 (or better)
  • RAM: 4 GB DDR3 (64-bit) (or better)
  • GPU: MALI T764 / 3D Graphic Engine (4K) (or better)

Previously validated devices

Make
Model
Preferred Deployment Method
ProDVX
APPC-10PXL
APPC-10DSK (supports LED bar)
APPC-10X-Series
APPC-10SLBe
APPC-10S (⚠️ See the note on this device below)
Client MDM
Client MDM
Client MDM
AV supplier or Client IT/MDM
DuoDuoGo
G20
Client MDM
Iadea
XDS 1078-A7 (supports LED bar)
XDS 1078-A9 (supports LED bar)
WRP-1000 (supports LED bar)
Client MDM
Client MDM
Client MDM
Elo
I-Series 4 for Android
AV Supplier or Client IT/MDM

⚠️ Note: For the LED indicators to work on the ProDVX APPC-10S device, the following configuration settings must be added:

  • Generate token in the ProMGR tool. The token remains valid as long as the user exists in the platform. If the user password is reset the token remains valid for 24 hours before being removed. If the user is removed, then a new token will have to be generated and updated in to the device configuration.
  • Add the token and other settings in the device configuration file:
"ProDVX_API_Type":1, 
"ProDVX_API_Token":"exampletoken string",  
"ProDVX_API_Settings":{
"API_BaseAddress":"localhost",
	 "API_Port":integer
      },
  • For the Unity colours to work via the API, the Colour_DeviceType setting must be set to 40.

Preferred deployment method

There are 2 methods of deployment that can be used to distribute IBSS Apps to hardware devices.

Client MDM

As these devices will typically be sitting on an IT network and within a client building, the natural ownership of the devices falls under the client IT department. Employing Mobile Device Management allows the IT department to centrally manage the security of these devices. 
By using an MDM tool, the IT department can centrally push the IBSS Apps to the devices. The app .apk file will be provided by ICONICS to the IT department for verification and deployment. 

AV Supplier or Client IT

Where ownership/responsibility of the devices does not lie with the client IT department, the AV supplier or client can deploy the IBSS Apps onto the devices. For this to work, the selected device must have an appropriate App Store on the device. Supported App Stores include:
- Google Play Store
- Amazon App Store

Device testing

As ICONICS does not supply hardware, we are only able to provide information on previously tested devices and cannot make recommendations on device suitability as this would typically fall under the remit of an AV consultant. It is advised that the applications are tested on a single device against a representative system before commissioning. A test device can be shipped to our offices for evaluation and verification that it will work as expected. Please contact the ICONICS offices for pricing.

Device setup considerations

Auto start-up

For Unity to start up automatically, add the app to managed configurations. Android now (after version 8.1) requires either an MDM or EMM to be used to configure which apps can be started up automatically. Unity does not support auto start-up as an in-app feature. It must be configured using MDM or EMM. Also, device manufacturers sometimes include an option to specify a start-up app.

Receiving state updates

Turn off the Sleep Mode in Android devices manually. In the Sleep Mode, it won't receive state updates from IBSS to properly function as a meeting room tablet and notify about upcoming meetings or warn about the needed check-in, for example.