It makes more sense to me to have the switches appear as red when the device has the ability to record you. When color is used as an indicator for something, the general convention is that red is negative. Meaning that there is a greater possibility of something going wrong when a red indicator is being displayed. You could argue that “webcam is not working for some reason” is a negative, and that seeing the bright red indicator can bring your attention to the switch as a hint to how to fix the issue. I would argue against that by stating that having a webcam record you when you do not want it to is a much bigger potential negative than the webcam not recording when you do want it to.
Also:
- When a traditional video camera displays a red indicator light, that means the camera is recording.
- On the underside of the Framework 16, the expansion module latches are red when disengaged
Technically, the color has always indicated the opposite of the expected default.
Passive indicators on switches like this historically have used the color to signify when something is disabled, because normally you expect that thing to be enabled. Look back to old devices with mute and disable switches like the old iPhones, Palm devices, etc. and the color always signified the thing being disabled. The default state is enabled, and the switch is disabling it.
Active indicators like LEDs being used on devices to indicate things like the mic or cam being on are generally newer. But even going back to things like the red recording lights, that’s because the expected default state was off, and the indicator was showing it was in a secondary state.
The color in both cases indicates the thing being controlled is in a secondary state, but the expected default state is different in the two scenarios.
Unless you consider firearms where red traditionally means the safety is off and the gun can fire.
Red = ded
If you don’t want ded, make sure no red.