iOS 15: Using coordinators to manage SwiftUI view controllers - Instafilter SwiftUI Tutorial 6/12

[@nonnnth]

Dog is just what I need in the middle of this moderately long tutorial ☺️

[@khrystyna_kost]

And it gets better when the second one appears 😅

[@clementcardonnel3219]

OMG this tutorial is amazing! Also the appearance of the beautiful doggo melted my heart. What an incredible team! ❤

[@olboone]

Your dogs are amazing! Love to see them on camera, don't apologise them for interrupting :)

[@SaghanMudbhari]

I hit the like button just because how you treated your dog. Respect!!

[@meet071]

Dogs are cute! And it's always pleasure to see them between. But when it's a video about some complicated topic, and we have to see more than a time to understand it, it becomes very annoying, getting disturbed in a crucial parts of video.

[@DK_MechE]

Great video as always Paul, but my goodness this has to be the most information dense one so far in the series.

[@DeniseNepraunig]

Great content as always Paul and I love your dogs soooo much :-)

[@magoomba]

thank you. was able to implement a custom delegate and coordinator with this

[@martinmajewski]

As a SwiftUI developer, I still need help wrapping my head around the difference between UIViewRepresentable and UIViewControllerRepresentable. Both protocols seem so similar, but I know that a ViewController in UIKit includes the logic and state of the UIKit view. However, I want to be able to have this logic and state inside an e.g. ObservableObject in SwiftUI. However, this seems not to work properly, as any changes to a binding between the UIKit view and SwiftUI are going to rerender the SwiftUI side. Which in turn does all weird stuff on the UIKit side because instances are dropped or structs are overridden. For example, I want to wrap MabBox Maps into an UIView(Controller)Representable, but I cannot establish a correctly working bidirectional interaction.

[@PureGlide]

Great tutorial, thanks! I've used this to wrap up WKWebView, but I can't figure out how to tell it to do something e.g. load a new URL. Do we have to do that through the coordinator also? or do I simply call a method in the wrapper object? but I don't have an instance of it from my parent Swift UI view? Cheers

[@HuyLe-hn9le]

thank you from the bottom of my heart

[@tigran.zakaryan]

where the context.coordinator with capital 'c' comes from ? how it's connected with the Coordinator class we are creating?

[@diegotrazzi]

I love. your content and I appreciate you explaining this concept which is somewhat difficult to grasp. I also love your dog, and I feel sorry for this, but maybe is my ADHD kicking in, but the dog (nose?) is distracting me so much 😣 I still don't understand clearly what happens after makingCoordinator() and how the "delegate" idea works: we bind the context.coordinator to the picker.delegate, but is the context something SwiftUI sends and how does SwiftUI know that the context has a coordinator ?

[@mzain823]

I learnt better because of those doggos there!

[@MikeWa1ker]

Love the dogs! 😊

[@leobonhart5824]

I removed the Coordinator inheritance from NSObject and the code seems to work just as before. Can anyone explain why do we need this inheritance and what it does, I can't quite understand it. Thanks.

[@coryjorgensen5385]

Why not just Bind against an SwiftUI Image so you don't have to load it from SwiftUI. Just convert it when it is picked?

[@umairkhan4982]

Great explanation

[@calebhermann]

Great content. This was very interesting to learn about.

[@kamertonaudiophileplayer847]

I also like the name Coordinator.

[@MoAdel92]

this tutorial is a little bit bewildering for me