android10 / android10/Android-CleanArchitecture-Kotlin

Data organization

Offen
#123 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Kotlin
Sterne
4.8k
Forks
929
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

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?

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.