android10 / android10/Android-CleanArchitecture-Kotlin
Data organization
- Ngôn ngữ chính
- Kotlin
- Star
- 4.8k
- Fork
- 929
- Chỉ số merge pull request
- Không có pull request nào được merge trong 30 ngày
Mô tả
Hey,
love your work, but I have an observation to add, from my experience.
It seems like everything is organized in "feature" packages (e.g. `movies`, `login`, etc.). This doesn't seem a good idea to me, since feature can sometimes require other data. Data required for a specific feature might not be 1:1.
For example, let's say you had a feature `songs` and `home`. Home screen would show most popular songs and most popular movies. How would you organize code in that case? Should `home` depend on other features - `songs` and `movies`? What if `songs` has no UI, should it still be considered a feature?
Hướng dẫn đóng góp
Chưa lập chỉ mục được hướng dẫn đóng góp cho kho mã nguồn này
Đánh giá
Issue này chưa được đánh giá.