Bluetooth Pairing Assistant
From a discussion about initializing a system that only has Bluetooth input (mouse, keyboard), we need to figure out when this occurs during initial setup or OS installation and what that looks like since obviously input is needed during these stages of getting started. Also relevant to when no mouse or keyboard peripheral is found.
Some open questions are: where will this UI will live and when/how the system will begin to recognize there are no input and when to begin to prompt/probe about devices to connect to.
Potential Workflow
For mice:
- in the background check whether there is a mouse available, if no mouse detected show dialog
- display dialog saying no mouse is available, and ask user to turn the Bluetooth mouse on, and show "searching"
- list all the discoverable devices, and when a mouse that's not paired/trusted is available, try to pair with it using the default "0000" as the pin
- if known mouse, show successful pair and dismiss dialog automatically if any mouse is plugged in/already paired and turned on and detected
For keyboards:
- in the background check whether there is a keyboard available, if no mouse detected show dialog
- display dialog saying saying no keyboard is available, and ask user to turn the Bluetooth keyboard on, and show "searching"
- list all the discoverable devices, and when a keyboard that's not paired/trusted is available, try to pair with it a PIN code that is generated, and wait for the pin to be entered by the user
- if known keyboard is detected, show successful pair and dismiss dialog automatically if any keyboard is plugged in/already paired and turned on
Relevant Art
Mac OS:
- wait for a bluetooth device to be found
Windows:
- [to be added when found]
Edited by Sam Hewitt