Now that users can have an artist badge in chat, I think this has traction to expand to other forms of community involvement such as developers.

The debate I can see right now is that should this be a per-channel basis like the way the artist badge is designed right now, or should this be a per-user basis for anyone who creates programs of any kind? For the former, the streamer already knows developers for their channel. For the latter, Twitch can reach out to communities who have already handpicked and curated well-known developers as well as continue to seek more developers.

The other thing to point out is what should it really mean when someone has a developer chat badge. There are many different interpretations. One could be an extension usage metric on channels. Another could be providing interactive overlays (excluding design). Another could be someone who does live coding streams. To some, some of those interpretations shouldn't be considered and to others, any of those interpretations and other interpretations could qualify them as a developer.

Regardless, I believe with some careful thoughts and planning of this, it would be really beneficial for the Twitch community as a whole.

I like this idea, makes me want to live stream some coding

I think it's going to turn into a badge chase. Everyone will want to become a developer and get a badge. In the end, Twitch has to spend a lot of resources to vet these developers. Is it worth it?

I have a few questions regarding this:
1: Are developers, people that take personal interest in developing things for twitch use in a non employed fashion? If so, there may be a conflict of interpretation here that would potentially result in abuse or misrepresentation. Individuals could claim they are developers and speak on behalf of twitch to those unaware.
2: Would this mark people offering hosting the badges as twitch endorsed individuals? This could have a similar issue to the above.
3: Who gains here?

One of the common pain points that I have seen for devs is access to features like channel points to test. As it stands, many have to ask and rely on others to test those features. The ability for those with a dev badge to be able to trigger things like sub notifications, or use channel points, would make this no longer a blocker. (and no longer a security risk for those being super helpful with the testing.)

Unfortunately, this would likely require increased scrutiny on getting the dev badge, and extra dev time beyond the approval process to implement.

Tradeoffs. /shrug

(Its also a reason for the badge to exist beyond "I want one")

This can be automated. If an app has *** amount of unique user request by the app's own ClientID, then give out the badge to the dev.

I love this idea! I was also thinking something along the lines of @LuckyNoS7evin's suggestion, that a chat badge should be semi-automated to save the hassle on Twitch's side, but I agree it shouldn't just be given to someone that signs into the Dev site. I was thinking either when:

* They create an Application (when they receive their tokens/secrets)
* They create an Extension (either when it's actually created, or when it's reviewed/approved by TwitchDev)
* They complete the Developer Onboarding process.

there is already the staff badge but I don't know if it includes developers

I don't think an automated system should be a thing for the badge. If it was, this would end up in it being the only badge that people can claim without doing anything, just like the GLHF badge. I feel like it should be intended for people who have made something that deals with the Twitch API, IRC or an Extension. A form would be nice. I feel like Extension devs already kind of "got accepted as devs", but I dunno.

The form could be like...

Twitch Name:

Type of applications you've made: Tool, bot, extension, etc.

Links to use/download your applications:

Or something like that.

@BlueLava

I agree an automated process is obviously better for Twitch and Staff so you don't have to curate a massive list of users and requests.

I do feel that just logging in to dev.twitch.tv is a little on the ”too easy” side of things.

I feel small tasks would be interesting to do.
1) create an app in the dashboard
2) create an extension
3) join the Twitch Dev discord and gain the developer role

You don't have to do all of these. The 3rd option leaves it more open as a community lead badge. This means the community can do the manual process TwitchDev are trying to avoid.

@BlueLava Ok, great!

@TwitchDev Community:

a) My first thought was: Not for bots. IMHO, they should be a different badge between verified/known bots and its developers. So users can easily see, this is a bot (a pice of software), and this is a real person (a 3rd-party developer).

b) How would one qualify: In my opinion, it needs to be automated, but it also needs a review process. If I had the choise to define such a guidline, I would formulate it in a similar way:

"You qualify for this badge if you have a published twitch extension or a verified bot. You will also need to have an account that has agreed to the Developer Services Agreement (you agree to this, if you signed up on TwitchDev)."

My background to this opinion:

Currently, Verified Bots as well as Twitch Extensions have a review process on Twitch. This is to prevent someone from simply unlocking this badge for fun automatically.

Con: It does not currently take into account of 3rd-party websites (oauth apps).

c) The automatic system should be possible (on the part of the chat team), iirc: anykey.org has a sign-up form, where you can fill you twitch id/username and you get instant the global GLHF Pledge badge (i also have this badge).

I would be pleased about further feedback!

@GhostZero Yup!

@TheRealHellcat The main challenge is figuring out what this badge actually means and there are many opinions. I’m making sure that past feedback on this topic is provided internally (there has been a lot). Providing the badge would need to be automatic, though I'm not sure how badge availably checks work personally. Something as simple as confirming a Twitch account has authenticated with dev.twitch.tv could work.

@TheElm Badges for the creator of integrations on a channel is a fun idea. If the badge is considered, I could see this either being the main logic or perhaps even a different badge altogether. A good thought for the chat team.

This would be cool to tie in with the official/known "Bot Accounts" or an Extension. If a channel is using an Extension, the developers of that extension get this badge in chat, or if a bot account is modded in the channel, give the badge to the developer.

Amazing idea, would love it!
How would one qualify, though?

@BlueLava Is this suggestion intended for 3rd party developers? If yes, I really love you idea!