Most sample projects out there show how to do a specific thing. How to display a List, implement push notifications, and what a basic architecture could look like.

But hardly any information is available on how to deal with an Xcode project at scale. A big codebase in Xcode has several properties that make it hard to get things right.

In the grand scheme, I consider code signing easier than setting up and managing a large codebase in Xcode.

One of the things I learned over the years is the basic principle of divide and conquer. It works for algorithms, it works for software architecture, and it works excellent for Xcode project management.

In my session, I will show you how to deal with large quantities of source code in Xcode. How to leverage Xcode itself, with a little help from Tuist, to create a project environment for your code that allows you to focus on what you do best: Implement the next feature or bug fix.

By doubling down on interface isolation, compartmentalization, and separation of concerns in your code. You can work with Xcode without waiting for ages to see a clean build complete.

When you join my session, you can expect me to present my best practices when working on large codebases. We go hands-on too. At the end of my session, you will feel inspired and ready to tackle a couple of issues in your Xcode projects that will make your experience with Xcode much better. Or maybe even change your entire Xcode project setup around.