The original title is: "Mono-Repo + Multi-Repo: How We Structured 6 Apps Across 4 Repositories"

Short summary

A team describes their hybrid repository strategy: a monorepo for tightly-coupled web apps and API, and separate repos for three mobile apps that ship through app store review. The split is driven by deployment cadence — web deploys in minutes while mobile releases take days — and reduces release-note noise and cross-team friction. They share practical mitigations for dependency drift, cross-repo issue linking, and onboarding documentation.

• •Web apps and API share a monorepo because features typically span both, enabling single-PR reviews
• •Mobile apps get separate repos due to app-store review cycles and independent versioning needs
• •Mitigations include pinned shared dependencies, explicit cross-repo issue linking, and identical branch protection rules

Generated with AI, which can make mistakes.