Beacons with an on/off button are popular in product and app development because they make it easier to test scenarios where a device goes into and out of range, without needing to physically move the beacon. This saves time during development and allows for more controlled testing conditions. The on/off function also provides a practical way to conserve battery life, since the beacon can be switched off when it is not needed, ensuring that power is only used during active testing.
However, it is important not to rely solely on the on/off button when testing how beacons move in and out of range. You should also run tests at the edge of the detection area to understand how your app behaves as the beacon repeatedly appears and disappears. This is particularly relevant on Android, where, unlike iOS in the background, the operating system does not enforce a minimum period that a beacon must remain out of range before being considered visible again. On iOS, it is equally important to test at the edge of detection when the app is running in the background or not running at all, to ensure you capture the differences in behaviour across platforms.
Another way of hiding beacons is to use a Faraday bag:
We have a web store category for beacons with an on off button.