android10 / android10/Android-CleanArchitecture-Kotlin
Data organization
- Lenguaje dominante
- Kotlin
- Estrellas
- 4.8k
- Forks
- 929
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
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?
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Evaluación
Este issue todavía no se ha evaluado.