I build Scriber, a one-handed BLE chording controller with a companion virtual keyboard (ScriberEditor, open source: github.com/Altomand/ScriberEditor). Three related asks for SPECS system input:

1. System-level BLE HID keyboards — pair once, type into any Lens or text field.

2. Custom input methods — let developers register their own virtual keyboard as a replacement for the system keyboard on text fields (like Android/iOS third-party keyboards). When a physical input device is connected, the system on-screen keyboard shouldn't pop up.

3. Tighter integration with the native Browser app — ability to pass field metadata (content type, current text) so a custom keyboard can adapt dynamically — different buttons or placement depending on the field, e.g. some keys changing to specific shortcuts when something is clicked. I'm happy to publish Scriber's virtual keyboard and accompanying code as an Asset Library package so the team has a concrete reference to integrate and test against.

Context: raised in an r/Spectacles thread with nick-ross (https://www.reddit.com/r/Spectacles/comments/1vfekba/will_the_ble_api_come_out_of_experimental_status/). I'll be at the SPECS launch event and developer session on September 16–17 and can bring a Scriber unit for the product team to test, if that would help.