Member-only story

Why you should use Xcode 16 buildable folders instead of groups

Thomas Ricouard
3 min readOct 24, 2024

I’ve recently migrated Ice Cubes, my open-source SwiftUI Mastodon client to use file system folders instead of Xcode groups.

The project was already split into multiple Swift packages; it was not a big lift. The only thing I did was to use the “Convert to Folder” command on every folder at the app level.

For this to work, you have to be sure that what you see in Xcode already reflects the folder layout. Unless you’re doing any custom / virtual organization within your groups, this should already be the case. Folders work exactly how they should; they just show (and compile/include) whatever is in the folder, just like an SPM package.

Folders have many advantages over Xcode virtual groups, so I think it’s worth enumerating them in an article so you can get the gist of it.

No more merge conflicts

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Thomas Ricouard
Thomas Ricouard

Written by Thomas Ricouard

📱 🚀 🇫🇷 [Entrepreneur, iOS/Mac & Web dev] | Now @Medium, @Glose 📖| Past @google 🔍 | Co-founded few companies before, a movies 🎥 app and smart browser one.

Responses (9)

Write a response

Quite useful tip in short and clear form, Thomas!
Indeed, virtual groups in .xcodeproj can be a huge headache, specially in larger teams, and this solution is much more simple and fine-grained than splitting the project in packages to reduce file creation / moving overlap among developers...
I'll try it asap 👍
Thanks!!

Bout Time! (This should have been this way back at Xcode 2.5.1! with Tiger 10.4.11!) heh

I thought folders was the default. I almost exclusively use SPM for Swift so never thought about it much. Indeed I thought Xcode16 introduced groups as an option.