Ensuring visibility into problematic areas of the codebase that require attention Local development experience and IDE usability.In our five years as a team, we have focused on these areas: The mobile developer experience team has grown from three people in 2017 to eight people today. They got together and formed an ad-hoc team to address the most common developer pain points. They thought that if they could make the developer experience for all mobile engineers better, they could not only help engineers be more productive, but also delight our customers with faster, higher-quality releases.

How it all startedĪ few mobile engineers realized early on that engineers who were hired to write native mobile code might not necessarily have expertise in the technical areas around their developer experience. In this post we will discuss why having a DevXp team improves efficiency and happiness, the cost of not having a team, and how the team identified and resolved some common developer pain points to optimize the developer experience. We have gotten a lot of value out of our focus on mobile developer experience, and we think most companies under-invest in this area. We use metrics and surveys to measure productivity and developer experience, such as developer sentiment, CI stability, time to merge (TTM), and test failure rate. At Slack, the goal of the Mobile Developer Experience Team (DevXp) is to empower developers to ship code with confidence while enjoying a pleasant and productive engineering experience.

Slack developer