This is a movies sample app in Kotlin, which is part of a serie of blog posts I have written about architecting android application using different approaches.
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?
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
songsandhome. Home screen would show most popular songs and most popular movies. How would you organize code in that case? Shouldhomedepend on other features -songsandmovies? What ifsongshas no UI, should it still be considered a feature?