Architecture: The Domain Layer - MAD Skills

In this episode of MAD skills you'll learn about the Domain Layer - an optional layer which sits between the UI and Data layers. Developer Relations Engineer Don Turner will explain how the domain layer can simplify your app architecture, making it easier to understand and test.

#Featured #Latest #MADSkills

product: Android - General;

[MikeJohnston]

2:39 - "If you're not using Kotlin, I'm deeply sorry for you"
Love it! 😅

[renascienza.bazarclub]

I love the approach of this chapter, because it draw attention to code that we aren't normally understand like business logic, but actually is.

[MoritzPost]

This series is really great and the description of the domain layer is spot on. Going down from ui -> domain (UseCase) -> data layer is really the right approach. Not enforcing it on the way up is also correct. These pass trough UseCases are not really necessary.

Btw, the example of the date formatting UseCase is not really the strongest as it does not have any other injectable dependencies. A novice user might not see the point in this first example. The second one is better though. Keep up the good work!

[oleksee]

Awesome! I have been using this approach for quite some time and still loved the video. It's simple, it touches debatable topics (e.g. ui directly acessing data, usecase to usecase dependency) and it's just simply nice

[YairCarreno]

I love all these series of articles and guideline designs. Thanks a lot, Android Teams; excellent work.🚀🥳

[Lpapadop]

what about domain models? api/dto models? should we do transformations? who is responsible for the transformation from dto to domain? the repo or the interactor?

[pvarela]

Deeply sorry for not using Kotlin, guys!! forget about Java, Kotlin is great!

[erfansn]

We enjoyed a great explanation of the domain layer

[loboplateadostacker]

This explanation makes it crystal clear.

[star-warsien]

This was great! Currently I don't use a domain layout outside of what you would call "Utils" classes. I like this approach though. I will definitely use in future projects.

[steel-r_ua]

VERY good explanation. Thank you, Don!

[brainy]

If there are people like me who understand just a little or nothing, keep watching n you will get things better. I understood about 50% of what he explained in this vd and this is by far the best.

[myrmecii]

I wonder if flow there can be replaced by livedata for the domain to UI communication

[Elidangerfield]

Question... The speake said to make the Use Case main safe but then made the invoke funciton suspended. ??

[daniyar]

Still confused, shouldn't that arrow go from data layer to domain layer?
Why domain layer have dependency on data layer? Isn't domain layer get access to data layer via repository interfaces?

[alinababenko]

I like your doc about Android Architecture. And videos about it. It's interesting, has some new details and explanations for me, I also found some my mistakes. Well-done. Thanks!

[phamhung]

Could you guys give me a simple project which has been using Usecase with Flows in best practice

[nicolasmanurung]

Do you have some resources, like the implementatiom of this video?

[arindomghosh]

One question: The use-cases only have functions and most of the times only one as shown in above example but no state, then shouldn’t creating a single instance of use-case suffice like we do for repo classes or is there a reason we need to create a new instance of a use-case every time we inject it?

[RafaelPerez-ninj]

I've been waiting for this series for a long time. I really like the simplicity of explanations and the way these approaches help us to write better code.