By layer or feature? Why not both?! Guide to Android app modularization

This is perfect, explains everything concisely while simultaneously being terse. Cheers.

How can i use firebase auth or firestore in separated modules instead of the app module ??

In my experience, when scaling to a large number of developers is better to avoid sharing business logic and data between feature modules. This may involve some duplication, but it can help prevent coupling and simplify maintenance in the long term.

I really don't see how the combined architecture solves the redundancy/code duplication problem. The domain:books still has no access to authors (Even though it can access the data:authors, it cannot obtain them with use cases/ re-used business logic) and suddenly the ui layer uses both domains? Does that mean that the GetBooksWithAuthorUseCase is implemented in the ui layer now? Really confusing

This was so poorly explained and I bet when the example comes out it will never compile just like all their other repos

🤩🤩🤩🤩

In a large codebase, additions to a feature data module cascades into changes to changes to other modules as well and in effect causes teams to block each other

Separate codebase by Feature module ending up with Clean Architecture

Data module depend on domain module not reverse I sure

Nice explanation.

Are you sure that the domain module depends on the data module?

Ok