The Model View Approach in SwiftUI

MVVM is the most proposed architecture of SwiftUI apps, but since apple has not released any official documentation on it there are some patterns that you can try and test to see if it could work with your project demands.

In this session we will talk about the model view approach in swiftui, and explore to see how it would work with a simple login module.

You must choose the requirement based on the project demands and if you have multiple approaches then please make a technical comparison between the approach and then make a decision.

I hope the video is helpful, please like subscribe and share it with your iOS group.

Given are the chapters in the video

0:00 introduction
0:10 demo's are not best practices
1:45 mvvm architecture pattern
3:46 model view approach
4:33 model view xcode demo
6:00 technical comparison is must
6:21 model responsibilities
6:51 model breaks separation of concern
7:24 model approach breaks abstraction
8:48 breaking model responsibilities
8:59 role of view
9:38 fruta demo
10:30 massive model issue
10:43 conclusion

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

✅ Subscribe to the channel and stay ahead of everyone by following the right way for writing clean code in swift. 🔥🔥🔥🔥🔥

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-----------------------------------------------------------------------------------------------------------------------
📥 Download the source code from

-----------------------------------------------------------------------------------------------------------------------

############################################

Connect with me on social media

###########################################
#swiftui #mvvmSwiftUI #swiftuiArchitecture

[CodeCat]

Hey there, I hope this session was helpful and if you have questions then please feel free to ask them in comment section.

[prataprana]

Great video and much needed..!!
The main thing is that what we see in demos or tutorials is not true for organisation and enterprise app code.
We should keep this in mind.
Thanks for sharing

[rasinsahaji]

I saw this model in the apple forum but I was unable to explain to the senior manager, now I can huge thank you.

[abhishekdhiman]

We appreciate your initiative in adhering to the principles we were taught. The chaos was loud.
let's hope heavy developers get convinced to consider beyond profit.

[tundsdev]

Great video, clear breakdown with a clear comparison too!

[nirajtiwari]

There was a buzz going on with this MV approach on Twitter and Apple Dev Forum so I watched this video till the end. As long as Apple doesn't provides any official way, there will come many opinionated ways to make SwiftUI apps, but in the end, we have to work in industry with best practises, using SOLID principles, design patterns with testability in mind to deliver quality apps. It seems to me that MV approach doesn't adds any value by violating software principles 😌. Will society accept me for putting this opinion 🤔?

[MultiGaurav]

I am very much thankful the way you are explaining each and every topics in details and in easy/understandable language . I request you to please make video for memory management attributes (Strong, weak, assign, retain, copy etc...) of objective for automatic & manual memory management which will clear many doubt of memory management for objective c developers.

[vishalmalvi]

Thank you for sharing this amazing video.

[Priyali]

Hi, please make video on VIPER architecture

[weekendNavigation]

What we should use for a client application which we are planning to start ?

[nidhitiwari]

I have a doubt it's not related to this topic but hope you give me the answer of Why do enum not have stored property???

[vishalbhai]

Very nice explanation. Thanks a lot.  
Which one is better Future or AnyPublisher for API Client method? Please give overview If possible.

[JockR]

Hey Mate...

Thanks a ton for this video and appreciate your efforts for making this video to clarify and make us aware that what needs to be done when it comes to make a decision while choosing Best suited architecture.

I personally came across this so called MV pattern on social media platforms and i was surprised and bit confused.

But this video clarified everything, definitely this is not the best practice as this gonna lead to massive and messed up Views.

Also from testing POV I think this MV pattern is disaster as there will be 0 testability.

Thanks again and hoping this pattern should not have any place in Architecture world... Cheers

[rasinsahaji]

One more question sir, if we use Uikit we can use the same view controller, with different ui code thanks to class type but how we can achieve that in Swiftui as it's struct I have no idea how we can achieve that, 3 text field to signup in Uikit I can inherit or conform and made that login page just hiding one text field and different button action (api call), I want to achieve that in Swiftui

[dharamveergupta]

I am a professional Sr.Android App developer, Should I learn iOS?
If not then what should I proceed with?