Видео

Thanks for explaining with a real world example , The explanation was spot on and easy to understand. Thank you

Thanks for explaining with a real world example , The explanation was spot on and easy to understand. Thank you 😊

Commend for min 07:00: Haven't you heard of VπJ world? 💣

Choosing java instead of kotlin may be good reason for china companies like huawei. Because they had faced play service restriction before and may not want put whole company under risk at the future.

Here is my argument for using Java: Why use Kotlin's coroutines when you can use Java's Threads and experience the thrill of debugging concurrency issues?

Happy holidays 🎄

Best video on this so far!

Thanks for clarifying. They should update documentation, the domain layer should be independent

Ευχαριστώ!

Very informative and good explanations. Thank you!

Great video!

This is good video, thanks!!!

Well explained. Thank you!

Thanks for sharing

Great video, one thing I noticed. Why aren't you using delegate for the remember? You'll skip writing .value to every state

Great explanation, thanks

Meglio pochi .a con contenuti validi come i vostri.Bravi

Happy to see you too!

Happy to see guys again

perfect

please make a video series explaining with a big app project showing all layers of architecture you prefer ui-viewmodel-usecase-repository-datasource in-between all of them can be interfaces use hilt dependency injection and may be viewmodel factory some question - where to put network not available switch i mean like if an app has local room db and api datasouse how one can switch between them and where to put this switch code is it in viewmodel or repository or dependency module or viewmodelfactory because if in future we have more datasources how will we switch easily

Here's my principle. An interface that has only one implementation is boilerplate. And if you like buzz words, here's one for you; Poltergeist: "The poltergeist anti-pattern occurs when we have a bunch of infrastructure code that serves the design but is otherwise useless." So, if it wasn't clear, I'm not going to add a bunch of interfaces in between my Repos, just to change the direction of an arrow on a PowerPoint slide. That's religion, not science.

thank you!!!, i just understand operator and invoke() from this explain

Very cool explanation! Subscribed!

Thank you for the video! This is very beginner friendly and has helped me understand what it actually is.

Hi Konstantinos, your videos are true gem. Always informative and to the point. Please make more videos covering different aspect of Software Engineering and Android App Development.

I would be a senior now if the documentation was written by you😅 Thanks for the video it was very useful

Thank You

Please make a tutorial on how can we achieve Clean Architecture in Android! People been doing MVVM with CA and I find it so wrong! I've been reading and watching a lot of CA concepts from .Net and I have no idea why android is so different from it.

Thanks for making this video!

Very helpful. How would this work if you are observing when a property within an object changes?

Best explanation of Clean Architecture I've heard in 9y of software development.

Interesting format! Loved the discussion.

This guy really knows how to explain things and make them easy to understand! Amazing job!

Best android developers out there! Great work 🏆 keep up the amazing contend!

Where goes the single responsibility principle when all the layers implement the interfaces from the domain layer? What about seperation of concerns? Why the domain layer should know what the data layer repository response should look like?

Great video!

Found your channel while searching for deep dive on IPC binders of Android. Went through a few videos on your channel & it's a gold mine for an android Engineer like me! Keep posting deep dives and good practices. Appreciate it much. Thank you! 😄

Loved the skits 😅

Happy to see you guys again

Hey, finaly new video🎉❤

So helpful, thanks!

great and well-explained

Initially I was not that clear with this concept. Thanks to you, now I have a solid understanding because of your remarkable explanation!

Great explanation! I finally got the concept of TDD.

Great, I am so hapy I discovered this chanel, Thanks a lot ❤

isn't repoimpl should be on a data layer and repo interface should be on the domain?

You're amazing. Thank you so much for contribute with your knowledgement.

Promo*SM

I just found your channel. and I love the content