android10 / android10/Android-CleanArchitecture-Kotlin

Data organization

Open
#123 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
4.8k
Forks
929
PR merge metrics
No merged PRs in 30d

Description

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?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.