How Modularity in Unity Projects Can Improve the Development Process

What the talk is about

Artem Korotenko explains how modularity keeps development speed predictable in Unity as a project and its team grow. His core idea: architecture should stop the cost of new features from rising over time, so a project should be designed from independent modules rather than from design patterns. Each module is an assembly definition with explicit dependencies. He covers the ban on cyclic dependencies and the stable-dependencies principle, using the swap of an analytics SDK behind an abstract module as an example. He then describes what makes a good module (easy to use and set up, with a clear interface), splitting generic from project-specific code, and moving modules between projects by copying folders or via the Package Manager, with its benefits and setup difficulties. Useful for Unity developers and tech leads on large or pipeline-style projects.