Since the HTML5 player would allow us to immediately support .mp4, .mp3, and .wav (72% of all video and 81% of all audio), we decided to move forward. Then, we worked with our Analytics team to figure out which file types were most commonly uploaded. We started by looking at the native capabilities of the HTML5 audio and video player. For most teams, this new feature was pleasant but minor, but for teams that work with audio and video files everyday, this saved both time and hassle.ĭetermined to ship this feature quickly, we knew we had to keep the scope manageable and that meant prioritizing and gaining efficiencies where we could. Previously, users would have had to download these files to play them. One improvement we launched recently was our inline media player, which enables users to play audio and video files that have been uploaded to Slack right within their channels and DMs. (Read more about what we’ve launched recently on our main blog.) Even as we’ve grown, we’re still committed to shipping features quickly and iterating rapidly with the help of new employees. This process has remained central to our team. If the problem is more complicated or requires a more involved solution, we’ll post the feedback in the appropriate team or product channel, where the right people can discuss it in more detail. If the issue at hand is easy to fix, we do so right away. When we receive actionable feedback from our users, we share it into a channel where anyone at the company can see the pain our users are feeling.
In fact, every engineer spends at least an hour per week supporting users alongside our Customer Experience team, as part of our Everyone Does Support program. At Slack, we’re focused on delivering big, impactful features, but we’re also dedicated to improving our users’ day-to-day experience of our product.
0 kommentar(er)
