Scaling Teams Mobile Development — Evolving the design pattern.

Monolithic mobile app codebases and stories about making them modularized is a common topic of discussion now-a-days. There are articles written on this from <a href="https://slack.engineering/stabilize-modularize-modernize-scaling-slacks-mobile-codebases/" rel="noopener ugc nofollow" target="_blank">Slack</a>, <a href="https://www.droidcon.com/2019/11/15/android-at-scale-square/" rel="noopener ugc nofollow" target="_blank">Square</a>, <a href="https://www.reddit.com/r/RedditEng/comments/vwrrrf/android_modularization/" rel="noopener ugc nofollow" target="_blank">Reddit</a>, <a href="https://robinhood.engineering/breaking-up-the-app-module-monolith-the-story-of-robinhoods-android-app-707fb993a50c" rel="noopener ugc nofollow" target="_blank">Robinhood</a> and many more. Here is a series of posts that provides a systematic way and a design pattern to modularize mobile apps effectively. This is especially applicable in an ecosystem where multiple partner teams works together in the same code base and compete to highlight and surface their respective features. This is part 1 of the series and talks about an effective design pattern that can be adopted for a modularized and easy to integrate code base, where multiple teams collaborate. <a href="https://medium.com/microsoft-mobile-engineering/scaling-teams-mobile-development-evolving-the-design-pattern-c3c8ff53facb">Read More</a>