android10 / android10/Android-CleanArchitecture-Kotlin

Data organization

Aperta
#123 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Kotlin
Stelle
4.8k
Fork
929
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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?

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.