Skip to content

Data organization #123

Open
Open
@WildOrangutan

Description

@WildOrangutan

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions