Architecture by team size
As an iOS team grows from 5 to 10 to 100 people, how should the way you manage code conflicts, quality, and architecture change at each stage?
As an iOS team grows from 5 to 10 to 100 people, how should the way you manage code conflicts, quality, and architecture change at each stage?
At 5 people, one target with a consistent pattern, lint, and CI. At 10, start modularizing, code ownership, interface contracts, trunk-based development with feature flags. At 100, a platform team, per-module independent build, test, and release, automated dependency rule checks, a design system, and DI infrastructure.
Build and distributionShort answerAdvanced
This one comes up onsite. "If you had to pick between a monorepo and several small…
#code-ownership #ci
iOS system designShort answerExpert
Design the architecture for an iOS app with tens of millions of users built by 60…
#team #modularization
iOS system designShort answerIntro
Several screens in the app (home, profile, settings) need the same "notification center"…
#team #modularization
TestingShort answerExpert
An app with 40 modules and 8,000 tests takes 40 minutes of CI tests. How would you change…
#modularization #ci