Difference between .xcodeproj and .xcworkspace, and when to use a workspace

WHAT THIS TESTS: This question checks whether you understand the structural hierarchy of Xcode's build system and how Apple organizes code, targets, and dependencies. A senior engineer should know that a workspace is not just a convenience feature but a mechanism for cross-project dependency resolution and shared build artifacts.

A GOOD ANSWER COVERS: First, define an xcodeproj as a single project document that contains targets, build settings, schemes, and references to source files and resources. Second, define an xcworkspace as a container that aggregates one or more xcodeproj files and optionally other workspaces, establishing a shared build directory so that projects can discover each other's build products. Third, explain the when and why: you need a workspace when using external dependency managers like CocoaPods or Swift Package Manager because they inject additional projects that must build alongside your app, or when you manually split a monolithic codebase into separate framework projects to improve build times and modularity. Fourth, mention that opening a workspace rather than the underlying project is essential because the workspace context provides the derived data path and scheme visibility for all contained projects.

COMMON WRONG ANSWERS: Saying that a workspace replaces a project or that you can delete the xcodeproj after creating a workspace. Another red flag is claiming workspaces are only for CocoaPods and have no native purpose in Xcode. Confusing schemes with workspaces or suggesting that a workspace merges the project files into one is also incorrect. Finally, stating that Swift Package Manager requires a workspace is wrong; SPM packages can be added directly to a project in modern Xcode versions, though workspaces are still common in hybrid setups.

LIKELY FOLLOW-UPS: How does Xcode resolve build dependencies between two projects in the same workspace? What happens to derived data and build products when projects share a workspace? How would you migrate from a single project to a multi-project workspace without breaking CI? Can you nest workspaces, and when would that be useful? How do CocoaPods and SPM differ in how they integrate with workspaces?

ONE CONCRETE EXAMPLE: Imagine you have an iOS app project and you want to extract a Networking layer into a reusable framework. You create a new framework project called Networking.xcodeproj and add it to MyApp.xcworkspace alongside MyApp.xcodeproj. You set the app target to link against the Networking framework. Because both projects are in the same workspace, Xcode builds Networking first, places the product in the shared build directory, and then links it into the app without requiring a prebuilt binary or manual search paths. If you opened MyApp.xcodeproj directly, the build would fail because the project file has no knowledge of the sibling framework project.