Twitch
Sign in with OpenID Connect
Sign in
prestine
Sign in with OpenID Connect
Signed in as (Sign out)
Close
Close
  • Sign in
  • Sign up
← Twitch UserVoice

Developers

Feedback

Developers

Categories

  • CATEGORIES
  • All ideas
  • My feedback
  • API 54 ideas
  • Developer Site 10 ideas
  • Documentation 3 ideas
  • Embeds 2 ideas
  • Extensions 15 ideas
  • Insights 2 ideas

JUMP TO ANOTHER FORUM

(thinking…)
  • Searching…

    No results.

    Clear search results
    • Accessibility 5 ideas
    • Account Management: e.g., Login, Connections, Password Reset 21 ideas
    • Ads 61 ideas
    • Bits 14 ideas
    • Channel: Panels, settings, profile, notification, etc 51 ideas
    • Chat/Messaging 135 ideas
    • Community Guidelines 9 ideas
    • Creators and Stream Features 69 ideas
    • Developers 87 ideas
    • Discovery: Browsing and Searching 204 ideas
    • Extensions 23 ideas
    • Game Mods & CurseForge 190 ideas
    • General 4,470 ideas
    • Localization 4 ideas
    • Moderation Tools 23 ideas
    • New Creator Dashboard 213 ideas
    • Subscriptions 45 ideas
    • Twitch Applications: Consoles 49 ideas
    • Twitch Applications: Desktop 937 ideas
    • Twitch Applications: Mobile 139 ideas
    • Twitch Applications: TV Apps 37 ideas
    • Twitch Con 2 ideas
    • Twitch Rebrand 7 ideas
    • Twitch Sings 4 ideas
    • Twitch Studio 142 ideas
    • Video Features 403 ideas
    • Video Performance 482 ideas
  • Twitch

How can we improve the developer experience on Twitch?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

Sign in
prestine
Sign in with OpenID Connect
Signed in as (Sign out)
Close
Close
Cancel Submitting...
  • or
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Improve the accuracy and precision of "hlsLatencyBroadcaster" in the Extension helper library.

    An improved "hlsLatencyBroadcaster" value unlocks and improves interactive experiences that rely on precise synchronization. For example, the Tobii eye tracker Extension and many Genvid Extensions that rely on this latency for accurate click or display location.

    53 votes
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    4 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  2. Channel point transaction in extension

    Like Bits transaction, it would be great to allow Channel points to be accessible from an extension.

    The idea is to not expose channel points to the extension and work the same way Bits transactions are.

    This would also need the addition of channelPointSku or allow sku product to have a bits value and/or a channel Point value.


    • User click on a button

    • Extension fires window.Twitch.ext.points.usePoints(pointsSku)

    • User validate transaction

    • (if user complete transaction )OnTransactionCompleted callback is fired with receipt containing channelPoint as the currency used

    • (if user cancel or don't have the channel Points) onTransactionCanceled is called

    To complete it, adding a filter on the endpoint GET helix/extensions/transactions would allow developers to only get Bits transaction, channel points transaction or both.

    Channel points in extensions would help people to discover features, interact with extensions more and at the same time, give a way to regulate the interaction by using channel points instead of free actions.

    Like Bits transaction, it would be great to allow Channel points to be accessible from an extension.

    The idea is to not expose channel points to the extension and work the same way Bits transactions are.

    This would also need the addition of channelPointSku or allow sku product to have a bits value and/or a channel Point value.


    • User click on a button

    • Extension fires window.Twitch.ext.points.usePoints(pointsSku)

    • User validate transaction

    • (if user complete transaction )OnTransactionCompleted callback is fired with receipt containing channelPoint as the currency used

    • (if user cancel or don't have the channel Points) onTransactionCanceled is called

    To complete it,…

    9 votes
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  3. Trigger events within Developer Rig

    Provide a method to trigger fake subscriptions/follows/cheers within the developer rig.

    8 votes
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  4. Add subscription status to Viewer's JWT

    Add subscriptionStatus to extension JWT. Currently subscriptionStatus is in Twitch.ext.viewer. With it in the JWT, it can be verified by an extension backend.

    8 votes
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  5. Viewer Only Extensions

    I was thinking, not all extensions need to be tried to a specific channel experience, and don't always interact with the broadcaster at all. Extensions like the chat translator, or maybe a TTS chat for viewers who can't read well, or visually impared, it would be great to have for users on every channel, not just channels where the broadcaster decides they want to use it. My idea is to have extensions that the view can enable on every channels, and possibly have the panel for viewer extensions be where the chat is, and possibly take up the bottom half of the screen, but same dimensions at chat, so you would have the top half of the screen be the chat, and bottom be the panel, or in a case like the translator, allow the viewer to have the panel take up the full height of chat. then the user can switch between their extensions similar to the experience on the streamer dashboard, and the drop down will be able to cycle through the extensions installed, so you can have multiple extensions running on every channel you visit.

    I was thinking, not all extensions need to be tried to a specific channel experience, and don't always interact with the broadcaster at all. Extensions like the chat translator, or maybe a TTS chat for viewers who can't read well, or visually impared, it would be great to have for users on every channel, not just channels where the broadcaster decides they want to use it. My idea is to have extensions that the view can enable on every channels, and possibly have the panel for viewer extensions be where the chat is, and possibly take up the bottom half…

    7 votes
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  6. Add the bits:read scope to bits enabled extensions

    I'm looking to add functionality to an extension where all bits count but bits within the extension have a weighting against those that aren't. I have my own bits transactions through the transactions endpoint but at the moment I have to ask for the scope separately. As my extension is already asking for the channel:read:subscriptions I thought it may be a good option to add this as an extra scope to ask for or possibly ask for within the same auth loop as the subscription read

    3 votes
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  7. Include username in onAuth callback when a user has granted ID access.

    Some third-party developers request id access on their Extensions just for the purpose of getting a viewer's username to build a more personalized experience. The only way to do so is by relying on the Helix user endpoint on their EBS. The Helix team already modified any payload that has a user id to also deliver a username and save developers the extra step of using the /users endpoint, so it's natural for Extensions to follow that path.

    3 votes
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  8. Standardize Transaction Timestamp in Bits Transaction JWT

    The given JWT representing the transatction receipt contains a time field that is stringified version of the Golang time object. Parsing in this format is significantly harder than a ISO standard format.

    3 votes
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  9. Include the user displayName in extension helper

    Include the displayName in the javascript helper without asking any special permision or without doing any special function (like using bits).
    This value it's only available if the user send bits and the transaction get complete.

    2 votes
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  10. Streamer whitelist removal after extension is live - [Beta release]

    Currently, if you launch an extension with a streamer whitelist, there is no way to remove this whitelist once the extension is live.

    I would like to suggest being able to remove (And only remove not add) the streamer whitelist once the extension is live. This will enable doing 'beta-releases', which is a very common rollout practice and has a lot of benefits for the developer.

    In this way a developer can release an extension to a set group of streamers who want to participate in the beta test.

    Once the developer has determined that things look good and it makes sense to open the usage to all streamers then they can remove the whitelist and do so. If however the developer sees that things arent working as expected or user behavior isnt positive, they can rework the extension and release a subsequent new version and restart the beta.

    This of course should not work in the opposite flow (Add a whitelist after an extension is live) as it could break for streamers who installed the extension but then werent in the whitelist once it was applied. So the ability should be one way. You can remove the whitelist after its live once but not re-apply it.

    Currently, if you launch an extension with a streamer whitelist, there is no way to remove this whitelist once the extension is live.

    I would like to suggest being able to remove (And only remove not add) the streamer whitelist once the extension is live. This will enable doing 'beta-releases', which is a very common rollout practice and has a lot of benefits for the developer.

    In this way a developer can release an extension to a set group of streamers who want to participate in the beta test.

    Once the developer has determined that things look good and it…

    2 votes
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  11. Allow Developers to Rollback to Approved Extension Versions

    Allowing developers to roll back a released version to another (approved) version would allow developers to quickly address breaking issues without going through a review process.

    2 votes
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  12. Allow Developers to Send Metadata with Bits Transactions

    2 votes
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  13. Improve Extension configuration design

    The current configuration page has a lot of empty space and on laptops, we lose half of the screen space instead of having a nice place to configure an extension
    See: https://discuss.dev.twitch.tv/t/improve-extension-configuration-page-for-smaller-screens/20194/3

    With the new design of the dashboard, Twitch introduced a new layout for the extension page.
    https://imgur.com/a/0SYGWi5

    It would be logical and great to have the configuration popup aligned to this design so we can have more space on the configuration page

    1 vote
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  14. include `game_id` in onContext not just the game name

    game_id would allow an Extension developer to make further API requests for a game with the required ID.

    1 vote
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  15. Allow pubsub whispers in Developer Rig

    The Twitch Developer Rig should support pubsub whispers. It current supports normal broadcasts, but not whispers to target a specific user's frontend.

    1 vote
    Sign in
    prestine
    Sign in with OpenID Connect
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Delete…  ·  Admin →
  • Don't see your idea?
Twitch
Twitch Terms of Service Powered By UserVoice

Your password has been reset

We have made changes to increase our security and have reset your password.

We've just sent you an email to . Click the link to create a password, then come back here and sign in.