Improvement for the product itself may involve making changes, but I am not aware of anything specific they are currently working on. The most painful part is that not all hardware supports virtual BLE. If you need to deploy a user engagement use case, you have to purchase specific SKUs that support BLE. Because of cost, Juniper offers non-VBLE devices and VBLE-enabled devices with the same specs, meaning you have two SKUs for the same model—one with BLE and one without. Therefore, if you purchase a non-BLE device and later decide to implement user engagement, you will need to change the hardware or make a decision from the beginning about whether you want to deploy user engagement. This is the most painful aspect.
Improvement for the product itself may involve making changes, but I am not aware of anything specific they are currently working on. The most painful part is that not all hardware supports virtual BLE. If you need to deploy a user engagement use case, you have to purchase specific SKUs that support BLE. Because of cost, Juniper offers non-VBLE devices and VBLE-enabled devices with the same specs, meaning you have two SKUs for the same model—one with BLE and one without. Therefore, if you purchase a non-BLE device and later decide to implement user engagement, you will need to change the hardware or make a decision from the beginning about whether you want to deploy user engagement. This is the most painful aspect.