Why Is It Useful:

Overwolf apps currently face limitations when trying to access native services like Bluetooth and Serial APIs, even with proper permissions. This improvement would streamline the integration of various hardware components into Overwolf apps, making it easier for developers to work with a wide range of hardware. It would foster the growth of hardware-related projects, promoting inclusion by enabling access to assistive technologies and physical devices that cater to diverse user needs. This could enhance immersion by allowing seamless interaction with microcontrollers and peripherals, and would promote more inclusive experiences for users, especially those who benefit from physical interfaces.

Who Would Benefit from It:

Developers working with hardware projects who want to integrate physical interfaces like microcontrollers and other peripherals into their Overwolf apps without the need for separate plugins. This would also benefit users by enabling a more immersive experience through direct hardware interaction.

How It Should Work:

Overwolf should expose access to Bluetooth, Serial, and other web-native APIs directly within the Overwolf environment. This could be achieved by ensuring these APIs work within the embedded Chromium context, with clear permission handling and pop-up support (e.g., for selecting a USB port) when required.