- Clean Architecture for SwiftUI
- Programmatic navigation in SwiftUI project
- Why I quit using the ObservableObject in SwiftUI
A demo project showcasing the setup of the SwiftUI app with Clean Architecture.
The app uses the restcountries.eu REST API to show the list of countries and details about them.
- Designed for scalability. It can be used as a reference for building large production apps.
- Vanilla SwiftUI + Combine implementation. No 3rd party dependencies
- Programmatic navigation (deep links support)
- Decoupled Presentation, Business Logic, and Data Access layers
- Everything is a
Struct(except for a couple of modules) - Centralized
AppStateas a single source of truth - Dependency injection of
InteractorsandAppState - Simple yet flexible networking layer built on Generics
- Handling of system events (such as
didBecomeActive,willResignActive) - Built with SOLID, DRY, KISS, YAGNI in mind.
SwiftUI views that contain no business logic and are a function of the state.
Side effects are triggered by the user's actions (such as a tap on a button) or view lifecycle event onAppear and are forwarded to the Interactors.
State and business logic layer (AppState + Interactors) are navitely injected into the view hierarchy with @Environment.
Business Logic Layer is represented by Interactors.
Interactors receive requests to perform work, such as obtaining data from an external source or making computations, but they never return data back directly.
Instead, they forward the result to the AppState or to a Binding. The latter is used when the result of work (the data) is used locally by one View and does not belong to the AppState.
Data Access Layer is represented by Repositories.
Repositories provide asynchronous API (Publisher from Combine) for making CRUD operations on the backend or a local database. They don't contain business logic, neither do they mutate the AppState. Repositories are accessible and used only by the Interactors.
