Daily iOS
Architecture

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?

How would an interviewer hear this answer? You'll see whether they'd move on, dig in, or say no, and which sentences would trip you up. Your score doesn't change.
See the short answer

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.

Share a question