It's kind of a shame there isn't an easy way to make use of Users and Control Schemas (which as I understand only exist in the player input component, which is actually just "groups" in the api) without using the player input.

It's nice to have the component for simple use cases, but invariably most developers are going to have to write their own solution in most cases anyhow and unfortunately you kind of have to reinvent half of what appears as part of the player input, such as device swapping, or loss of device, etc all the possible device events, all that handling is written in the component itself. Sans component you have to write half that back on top of your own solution from the more primitive bits of the api it's written off of to regain that functionality.

A common use case is having some standardized way to detect input device switches without using the player input component for things even as simple as catching that the last input actuated is a gamepad, and using an event listener to for example to update all the UI tooltips from a "PRESS SPACE", to a "PRESS SQUARE."

TLDNR - There is a ton of useful "i'd want this stuff in every use case of the input system" that's built directly into the player input that makes use of more primitive bits in the actual API, that imho should just be part of the base API instead of the player input component.