Hey there, I hope this session was helpful and if you have questions then please feel free to ask them in comment section. iOS cafe invite link: discord.gg/gB3mhP8DNq Download source code shown in the video from GitHub: github.com/codecat15/RU-vid-tutorial/tree/master/SwiftUI/ModelViewApproach
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 🤔?
The thing about developer forums is that the content that’s being discussed is not officially from apple, rather it’s a suggestion or perhaps an opinion. In programming domain if you decide to use a approach then that approach/suggestion needs to be tested throughly to make sure it adheres to all coding standards or at least does not break any object oriented principle. And maybe for saying this out loud the creative developer community won’t accept you or me both 😂😂😂
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
I did a video on career guidance for senior developers, it’s not specific to iOS but will surely give you a path to what to next & plan better ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-MpFe0AaIsgQ.html Hope it helps, please do ask questions if you still have doubts
I try note to use that monstrosity as it's immense pain to build all those layers for no reason for a simple app tbh, but then I am still trying to learn and find reasons as to why folks use this pattern over something that's simple and more manageable to maintain, it almost feels like over-engineered
Yes app architecture, mvvm or viper or mvp , this application should be in iOS I i-watch and iMac all 3 platforms a bit complex ui means it have graph etc like a stock market app
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.
there's a video on ARC, weak and unowned keyword, copy on write which will explain you those topics, I have not covered assign and retain, I guess I have touched few aspects on retain in the ARC video so its kind of scattered across than having a dedicated video.
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
I agree, imagine using this in a large complex app, not sure what other principle will it break, when we deal with complex use cases, The matter of fact that it breaks abstraction it raises a red flag in my mind that maybe you should not be having functions in the model. There’s a reason why good code principles exists and are proven to be beneficial over decades and have stood strong the test of time.
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.
Maybe folks who care about coding principles and code maintainability won’t use this MV approach. Even if this is used, then I won’t be surprised if this becomes an anti pattern because of all the principles it breaks.
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
@@CodeCat15 sir all I want is to achieve I want to create outlet once and I will use that in multiple places without writing everything, I can achieve that in Uikit thanks to class but I don't know is that possible in Swiftui struct
