Using Design Patterns with SwiftUI | Swift 5, Xcode 11

Today Kilo Loco goes over how to use your favorite design pattern (architecture) with SwiftUI. We cover how to handle passing data from both networking requests and Core Data to your SwiftUI ContentView.

This video will be helpful for anyone curious as to how they can pass data they decode from JSON or fetch from a persistence service like Core Data, Realm, or SQLite. It also goes into depth about the changes you may need to make in your current design pattern, whether you're using MVC, MVP, MVVM, VIPER, or CLEAN.

*** Show Notes and Links ***

Project Files:

Need Help?

Data Structures & Algorithms Book:

More Books:

Kyle Lee on Social Media:

---------GEAR -------

Code Passionately T-Shirt

Laptop - 2017 MacBook Pro

Keyboard - Anne Pro 2

Microphone - Blue Yeti

DISCLAIMER: This video and description contains affiliate links, which means that if you click on one of the product links, we’ll receive a small commission. This helps support the channel and allows us to continue to make videos like this. Thank you for the support!
#swiftui #swiftlang #iosdev

[TheKeef]

First of all, glad you are back after what must have been a really traumatic time for you. 

I found this tutorial really helpful. It aided me to a breakthrough in my own understanding. It's the first tutorial I have seen that begins to show how to architect a clean app over doing clever UI stuff with views. I can't wait/really hope to see you follow up with a second instalment to clean up with scene delegate. Your knowledge and teaching style have improved so much btw. It was a joy for me to watch this video.

[cary]

Thanks Kilo for an excellent tutorial tying together data service requests, user source of truth, and SwiftUI. Best wishes on all your next steps!

[RobertHolzapfel]

Thanks for coming back, serving us with inspiring - ok I should say "passionate" - coding. 👍🏻

[alobaili]

Wonderful video. I wish there are more videos focusing on architecture and ways to keep a project neat and SOLID.

[joesephf]

Wow, you opened a whole new chapter in SwiftUI for me, great tutorial, like always, it was so sad to hear you were laid off from your job, but we are happy to have you back :D

[stephinline]

You’re an amazing instructor and I’ve learned so much off your videos. Thank you for the great content!

[chaceteera]

Really inspiring to see you moving forward onto your new adventure so soon. Good job!

[belafekete]

Hi, it's great Kyle! Excellent tutorial! I'm glad you're here again!

[folivif]

Great to have you back bro. Sorry about your previous job

[nizzm]

Please do more on Combine framework, your content is another level 👍

[mukulbakshi]

It's Your boy Kilo Loco Love U man, love to see you back (;

[rileander]

The Vidya Ive been waiting for! Thank you

[erezhod]

Very nice architecture style and explanation!
I would rename the "{Feature}SourceOfTruth" classes something like "{Feature}Repository". Other than that, great tutorial overall 🙂

[tamizouine]

hello kilo loco, keep going I'll start the swiftUI with you

[CraigSchubert]

Great video - thanks!
I've struggled to get my head around how architectures actually look like when they're implemented and this was helpful. :-) (Still gonna have to go back over it to pick up more though...)
I would love to see how you would pull out the view controller code like you talked about at the end...
Cheers!

[RomanFromromeDotCom]

Great stuff man! Thanks for sharing and keeping it running :)

[igorbeaver]

Nice video. But I just don’t get why do you need this separate sourceOfTruth class. It seems that it’s just a part of the model isn’t it? And what pattern officially has this sourceOfTruth layer?

[isaacclark]

Great content. In fact, this is probably the best SwiftUI content I have seen. Were you using SwiftUI at your last position?

[YouBetterBeJedi]

Nice video and a nice view to work with view controllers in SwiftUI. But somehow it feels like an anti pattern for SwiftUI and a lot of boilerplate code . There are better approaches? I would prefer some kind of dependency injection over environmentobject/property wrappers. Or a Redux pattern

[embassem]

thanks for that great video,
I have a question about the reference cycle,
should we access the sot from the view directly?
or the VC is the one who should own the sot?