Likewise, all network operations were rewritten to use an internal connectivity framework. In addition, they had to rewrite some code that accessed Core Data directly and make it use their own Core Data-based persistent framework, which improved performance and stability. According to Slack engineers, the coexistence of Swift and Objective-C code in the same project made compilation slower and impacted performance, but mostly hindered the adoption of new Swift language features due to interoperability requirements. On iOS, it included rewriting in Swift the remaining parts of the app that were still written in Objective-C. Stabilization was the first, enabling step. To accomplish their result, the team devised three different goals: stabilizing their codebase to get rid of the tech debt modularizing the apps into separate components modernize their design and tech-stack commitments.
After discarding the idea of a complete rewrite as well as of reusing code across platforms, they decided for a complete refactoring.Ĭhoosing this option did mean that we had to deal with our existing tech debt - we had to migrate our legacy code and re-architect the apps in place, while keeping the app shippable and continuing development of new features. When Slack engineers decided to revamp their iOS and Android apps, they had to face the reality of two several year-old codebases that had grown organically and accumulated a significant tech debt over time. Among other things, this enabled a full switch to Swift for iOS.
Slack succeeded in the effort to bring their iOS and Android apps up-to-date and adopt new design trends.
0 kommentar(er)
