In the early days, Slack workspaces tended to be fairly small: clients were able to fetch most of the data about a team each session and backend APIs could return complete data about a team, or send events to every user when any property changed. Part II of this series, about Modularization, is here part III, about Modernization, is here Background In later posts we’ll discuss the other phases and the results. This is the story of the first stage of the cross-functional initiative we launched to solve these issues. These were questions we grappled with at the beginning of 2020, when we realized that tech debt in Slack’s mobile codebases had slowed development down enough to affect product roadmaps, and it would take a major refactor of our codebases to address it. How can you make significant architectural improvements to a complex application while still continuing to ship features?

What is the best way to address widespread inconsistencies and outdated patterns? When do you need to overhaul a large code base to address tech debt?

Slack mobile app technology