Digital Asset Library & Asset Managment
The team and I used this redesign as an opportunity to completely rethink digital asset management on Twitch. In addition to redesigning the emote and digital asset management experience we introduced brand new functionality including a staging/storage library, drag-and-drop slot assignment, and emote approval status indicators.
Managing Digital Assets on Twitch is frustrating and unpredictable
Unintuitive navigation and inconsistent information hierarchy for similar experiences is creating confusion. Related assets (such as emotes versus bits tier emotes) are segmented across multiple pages causing discoverability challenges.
Users want a dedicated space to upload and store all asset types. Improving navigation and consolidating asset pages would remove the dependency on 3P tools, make it easier to locate and manage all custom content, and allow creators to:
• Discover new types of assets as they are launched
• More easily locate and manage custom content
The inability to save historically approved assets makes it challenging for streamers to respond to the needs of their communities quickly, and de-incentivizes the creation of new content. Requiring that users re-submit previously approved emotes when updating live slots contributes to a high-friction experience.
Digital Assets Home
Digital Asset Library
Standard Asset Interactions
Our usage data revealed that Creators often swapped emotes on-the-fly in order to give their subscribers a constantly refreshing emote offering, often including seasonal or limited-time emotes. Through UXR interviews with Creators it became clear that the our lack of on-platform staging for unused emotes made this behavior needlessly complex. Creators wanted a place to store all their emotes and easily swap them in and out of tiers without having to delete and reupload every time. This was one of the driving insights behind our introduction of a digital asset library within the Creator Dashboard.
Twitch's existing upload form was clunky and confusing, and didn't scale to accommodate different asset types like Animated Emotes. I introduced the Upload Modal as a pattern that could scale to accommodate different upload criteria while providing a consistent experience across asset types.
Edge Cases & Error States
As part of our design and developer-handoff processes, we cataloged every interaction including error states and edge cases.