Your question is Patterns for Scaling Codebases. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
What architectural pattern would you choose for a rapidly scaling mobile codebase at Suno, and why?
Explain the layers or modules you would introduce, their ownership, dependency direction, dependency injection approach, and state flow. Compare your choice with at least one viable alternative and describe how it supports maintainability and testability as the codebase grows.
