Back to project foundations
Reference project
Clean Architecture SwiftUI
SwiftUI reference app showing separated presentation, business logic and data access with SwiftData persistence.
Why we recommend it
It is useful when planning a native Apple-platform app whose interface and data layer should remain independently testable. The countries demo makes navigation, dependency injection and state management concrete enough to adapt thoughtfully to your own product.
When to choose it
- Native SwiftUI apps with persistent data and a clearly separated domain layer.
- Teams comparing architecture and test patterns before implementing customer or employee workflows.
What to consider
- This is a countries demo backed by an external API, not a complete business application or authentication starter.
- Adapting it requires replacing the domain and checking Apple deployment targets, SwiftData requirements and dependency compatibility.
Start with this project
Open the project with a compatible Xcode and Apple SDK on macOS. Review the demo's data API and package dependencies, run its tests and explore navigation and persistence. Build your own domain and authentication flow separately instead of retaining the demo's assumptions.
