Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/admkopec/rickmorty-tca
A sample iOS app using TCA and Clean Architecture best practices
https://github.com/admkopec/rickmorty-tca
swift swiftui the-composable-architecture
Last synced: 6 days ago
JSON representation
A sample iOS app using TCA and Clean Architecture best practices
- Host: GitHub
- URL: https://github.com/admkopec/rickmorty-tca
- Owner: admkopec
- License: mit
- Created: 2024-06-15T19:09:56.000Z (6 months ago)
- Default Branch: main
- Last Pushed: 2024-06-20T13:34:24.000Z (6 months ago)
- Last Synced: 2024-12-14T23:48:47.751Z (12 days ago)
- Topics: swift, swiftui, the-composable-architecture
- Language: Swift
- Homepage:
- Size: 62.5 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Rick & Morty
A sample iOS application using [The Composable Architecture](https://github.com/pointfreeco/swift-composable-architecture).
The application uses the [The Rick and Morty API](https://rickandmortyapi.com/documentation) to display list of characters and basic information about them.
The application aims to be modular following Clean Architecture guidelines and implementing repository patterns or separate worker classes for more advanced application logic. The Views are composed using TCA with the minimal business logic provided as part of Reducers. They connect to workers and repositories via TCA's Dependencies which unfortunately have to be provided as bridging structs due to TCA's inner architecture, and I am against writing complex logic in closures :)
## Features
- Infinite scroll pagination and `LazyVStack` for minimising the memory footprint of the application.
- `AsyncImage` for loading thumbnails only when needed
- CoreData storage for keeping track of "Favourite" characters
- `.searchable()` modifier for character searching
## Disclaimer
This is my first and only iOS project using TCA. I greatly appreciate the macros and extensive documentation including tutorials offered by this architecture. However, the way it implements reducers and dependecy injection, in my opinion greatly hinders code readability. This is why, I will most probably stick with Clean Swift or a variant of MVVM for my personal projects.