Android Architecture Patterns - MVVM, MVP, MVC in Android | CheezyCode Hindi - #14 

You're very welcome!

You're welcome 😊

Thank you...will definitely try..👍

Thanks Sunil

😀 Thank you bro

🤘

Thanks Harsha

@@CheezyCode can I ask how you had learned these concepts in the first place?

1. Read a lot. 2. Implemented everything I learn. 3. Small projects, silly mistakes, multiple errors, fixing those errors - makes you confident. Last - storytelling is a skill. Acquired over the years. Jaisa aap khud samjhte ho dimaag mei , wo shabdo mei utarna hai...jab tak story nahi hogi dimaag mei cheezein stick nahi karegi 🤘

@@CheezyCode thank you:)

Thanks Ashish

Thanks Pratik 👍

Thanks Sahithi...Keep supporting 🤘

Will do 👍

Thank you Abhimanyu ✌️

Thank you! 🙂

Thank you 🤘

Yes or no - depends on how you have written the code. Ideal way is to have interface that calls the methods on the view There is no one stopping you to access views in case of MVVM but as a good practice we generally avoid. Same applies to MVP as well. Hope this helps.

Thank you 🙂

Room ke liye sirf room...sari videos independent hai

Last song release karna hai...video pe stuck hai

Cheers 🤘

Thank you Vipin 👍

Project structure se generally you can determine. If that does not work - check few classes. Concepts like Use cases, Interactors will be there for clean architecture...rest future mei will add videos on clean Architecture

yes plan yehi h - ek app ko 3 architecture se banake dekhe - difference jyada clear hojayega

Thanks Anas 😊

Thanks Vaishnavi

Thank you. Please help us reach more people. Share if possible 🤘

thanks bro - koshish karte hai...aajayenge iss level pe jaldi 👍

Thanks Anurag.

Yes you can.. Convert your controllers to presentation logic and define observables... If Views need some data, then observables will expose data with the help of observers.. And you can wrtite test cases for each layers.. In this way seperations of concers is maintained and your app will be easily maintable.

Thanks a ton 👍

yes api is node js is in progress - will post soon

Question nahi samjha aapka

@@CheezyCode sir mare already study mate MVC & MVP Architecture pattern theory & practical just understand purpose in kotlin ma joie che

you are It's Topic available video plz send me

@@Dhruv_Kikani_0101 bhai...atlu simple to samjave che..practical terms ma first try how can you write test cases pachi aa patterns thodu easily samaj ma avse.. Badhuj test cases tme lakho ena pr che.. plus tame expose kro data ne to ema without affecting each layer how you can expose e try kro....chat application jevu kaik bani shake...

Nope...view cannot directly interact with model... controller sits in between model and view.

problem kya aa rhi h? check the configuration on developers.android.com

Will start with Dagger

Noted...

Now start to build app..

SOLID is a way to achieve separation of concerns.

50K pe share kardenge 😊

Thank you Prakhar

Koshish karte hai..samay ki pabandi hai bro

Thanks Aditya

Data flow ke sense mei bola hai dependent. Architecture koi bhi follow karlo. Coupling aur cohesion developer ke haathon mei hota hai... For instance, ViewModel ke andar views ka reference hold kar skte ho...no one will prevent you from doing so but that makes them tightly coupled.

Up and running ✌️

Sharvan bhai shuru kiya hua...unpe rok nahi lagegi...raftaar poori hogi un videos pe

Thanks 👍

dedicated video banate h ispe

bro 50k pe live karne ka try karege

@@CheezyCode Then i hope jaldi ho jaye