The project I work on follows a similar convention, but the project is huge, and we've found ourselves tangled in a web of packages all separated by function. Is there a reason you suggest this navigational structure instead of feature-based?
I guess I find it useful to look at my packages and files and know by their names to what activity/fragment/adapter etc they correspond to, however, I understand your point that in a really big project one might end with a LOT of files. It really depends on the size and scope of the project. I guess you could choose whichever you and your team feel comfortable with as long as it fits with your team's standards since the ultimate goal of setting a structure is to make it readable and maintainable to those who will work on it.
I know it's a very general answer, but still, hope it helps. And thanks for reading the post, hope it helped as well.
gradle allow to configure multiple ressources folders antonioleiva.com/android-multiple-...
Useful! Thanks for sharing, I'll definitely check it out!
I also follow this convention. Great post 👍🏾
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.