I like the detail you go to in your post, but I’d like to add my own points to it:
- I agree that official libraries would be amazing, but in my past experience, I have been a lot more opposed to using an “SDK” of sorts a company publishes instead of rolling my own code as it always does things in ways that are not always quite what i want or feel like they “bloat” my needs - I don’t always want to run a local webserver or connect to pubsub when all i need is to exchange an id to a name.
- While a Sandbox environment would definitely be amazing, i personally would prefer the mock approach i can run and setup myself. It feels like i am more in control of it that way. Also I do think that a sandbox environment would be a more complicated solution to build from Twitch’s perspective, as it costs them more resources compared to letting everyone run their own one.
- As for “trigger test webhook with this payload” - that’s exactly what the CLI already does - at least for eventsub. I only recently touched eventsub for the first time myself and the CLI was a great way to verify I did the correct thing. Discord had a similar thing, though it was integrated into their oauth client configuration (for slash commands, when you set your callback URL in the web console, they send you a verification payload, allowing you to verify you did things correctly.)
- I agree that the docs must be kept up-to-date.