What problem does this solve or what need does it fill?

As shown in https://github.com/bevyengine/bevy/blob/main/examples/input/gamepad_input.rs, we need to track when gamepads connect.

The GamepadLobby shown there is a common and useful abstraction: external crates should be able to coordinate around its existence (and end users shouldn't have to copy boilerplate from examples).

What solution would you like?

Make GamepadLobby a built-in Bevy type and export it.

Add connection_system from that example to CoreStage::PreUpdate as part of the appropriate plugin.

Update the examples to use this new type.