Clean Architecture in Android in 5 minutes
Рет қаралды 19,667
Күн бұрынClean architecture is very important in the software development. A lot of companies are interested in finding people that know the concepts of Clean Architecture, SOLID, clean code among others.
Here I explain about it.
If you have questions let me know!
If you wanna know how to implement it in a real Android app check my course.
Link for the course:
~ 📚 bit.ly/cleancoderenaro
If you prefer access to unlimited typeof courses, try Skill Share instead, first month is FREE:
~ 📚 skl.sh/3Rak14w
If you wanna follow the course and can't afford it, send me a connection on LinkedIn and I will share the course with you for FREE!
LinkedIn: / renaro
Link for the code in github:
~ github.com/renaro/ecommerce-a...
@cosmicdioxide 25 күн бұрын
Wow thank you! Such compact yet very clear explanation
@DanielIderiba Жыл бұрын
Thank you for the video. Your explanation was quite clear despite the content being quite complex. I confess I must see the video 2 or 3x to absorb the content. Helped a lot!
@sulemankhan523 Жыл бұрын
Thanks for the great explanation Also autogenerated subtitles are perfect in your videos, thats really great too
@Renaro Жыл бұрын
Glad to read this!
@sebastianvargas2517 9 ай бұрын
Hey Renaro, great video! Thanks for explaining it so simple!
@devnagringa 9 ай бұрын
Happy that you liked it.
@Renaro Жыл бұрын
Hey people! In my next videos I will make a challenge with 3 of my subscribers. The winner will get 200 US$. If you want to participate, add me on LinkedIn. First come, first served.
@abhasarya7152 Жыл бұрын
wow, fantastic explanation!
@Renaro Жыл бұрын
Glad to read!
@mohamedkissicamara7518 2 жыл бұрын
Nice Video you just gained a sub
@Renaro 2 жыл бұрын
Glad you liked!
@pryscilla.rodrigues 2 жыл бұрын
Nice video!
@Renaro 2 жыл бұрын
thanks! :)
@nguyencodervn Жыл бұрын
THANK YOU
@Renaro Жыл бұрын
Happy that you liked it
@rijalmyd 2 жыл бұрын
Hai, sir. Could you give a simple example using Single Event for live data with Repository?
@Renaro 2 жыл бұрын
In the description I added a sample project, what are you looking for exactly?
@subodhrai1988 Жыл бұрын
awesome
@jmorasot 2 жыл бұрын
Hey bro, nice video, could you add references of your info? Also could you create videos of unit testing and clean architecture, please? Thanks a lot!
@Renaro 2 жыл бұрын
I am glad you liked. The ideas came from this book: Clean Architecture: A Craftsman's Guide to Software Structure and Design, really recommend. I will try to create some videos about unit testing, I explain about it in the course(description) but I do not have some videos about it yet.
@jmorasot 2 жыл бұрын
Great work, I’m going to check that book and some testing in your channel will be awesome. Thanks for take time to answer!
@aneeshpeakpointz Жыл бұрын
Great video nicely explained ❤️
@rithulraj3348 Жыл бұрын
Where should we put service, broadcast receiver, work manager etc
@Renaro Жыл бұрын
They are the implementation details of "a repository" so they should go in the data/repository layer
@jackli1924 4 ай бұрын
awsome！cool！
@name1566 11 ай бұрын
Understood
@ArturoDevA Жыл бұрын
no deberia haber ninguna instancia de un repository en el viewmodel, ya que es el caso de uso quien se comunica con el repository
@Renaro Жыл бұрын
Good point, very often Use Cases does nothing but call the repositories, if there is no "use case" for a use case then there is no problem having a repository in the viewModel, as long as the repository is an interface
@neldse 2 жыл бұрын
Ideally usecases shouldn't depend on each other.
@Renaro 2 жыл бұрын
I think you are right, then changing one use case might affect others...
@Abhishekdubey-mn8up Жыл бұрын
Use cases can depend on each other. As per Google recommendation in MAD skills architecture video with domain layer.
@neldse Жыл бұрын
@@Abhishekdubey-mn8up They are wrong you shouldn't do that. Imagine a scenario where you change the behavior of one usecase then you might have to alter the calling usecase as well. Follow the clean architecture and solid principles not the MAD skill
@Renaro Жыл бұрын
I think both points are valid, in some cases it might be useful and desired to change the behaviour of all use cases that use some use case, otherwise we would have to duplicate the code. But you do have a point that we should be aware of this dependency and when it might not be desired.
@user-nd8dk8ns3z 8 ай бұрын
Stop calling Android architecture principles from google documentation "Clean architecture". Android documentation make it clear that your data layer is the most important/source of truth etc. In real clean architecture you make Repository an interface located in domain layer. That way you follow Inversion of Control principle to make domain the most important layer in your application. It is very frustrating and brings a lot of confusion. By the way it does not mean that architecture in your video aka Google recommended architecture is wrong, it is just not Clean Architecture from Uncle Bob book.
@jackeblan 4 ай бұрын
I agree. This is not Uncle Bob's CA. This is just a modified MVVM.
Android Developers
Рет қаралды 42 М.