Navigation in SwiftUI & iOS 16

[@markaurelius61]

This is the first time I had seen NavigationPath, but I think that is what makes NavigationStack useful

[@FloWritesCode]

For sure. This is what really enables programmatic navigation with little overhead. It's also doable without NavigationPath, but needs a bit more setup.

[@FloWritesCode]

These changes are SO GOOD! Thanks for letting me host this lesson😁

[@CodeWithChris]

Wunderbar! @AdrienVillez

[@bigmtnstudio]

Thanks for the mention, Flo. 🤗 Awesome overview!

[@ninumedia]

Excellent tutorial and really appreciate the thoughtful examples. I learned multiple things I didn't know already. You earned a new subscriber.

[@jamesallison9725]

Wonderful!! This is the best Navigation Stack tutorial I have found so far. Thanks - I am subscribing right now.

[@CodeWithChris]

Awesome, thank you! - Pat

[@gondaimgano]

I love UIKit Storyboards but this new Navigation for SwiftUI is a game changer.

[@CodeWithChris]

It really is. Thanks for watching! - Pat

[@gondaimgano]

@@CodeWithChris thank you to you!

[@chrisstromberg6527]

This is probably one of the better explanations on SwiftUI Navigation that I have seen. There are some other great online instructors for SwiftUI, but they all pretty much dropped the ball on explaining NavigationStack.

[@CodeWithChris]

Thank you for the kind words! :) - Pat

[@ColeDano]

Oh this is huge, navigation was a buggy mess. Nicely shown @Flo writes Code.

[@CodeWithChris]

Great!! I'll pass the message along! Flo has a bunch of videos on his own channel to by the way! (kzbin.infovideos) @AdrienVillez

[@EricTMCode]

What a great Navigation Stack tutorial, thank you 🤩

[@CodeWithChris]

Glad you liked it! - Pat

[@japonska2009]

so if i understand this correctly(as a beginer in SwiftUI), when i am in between the lines of navigationDestination, i can already make a new ContentView design with Z/V/H stacks and add Spacer and all of that stuff for all the data i got from 1 Navigation Link(here would be some API data i got from the web)? I hope this is understandable

[@APWatchdog]

Very useful video. Can you elaborate on how NavigationLink would work inside a Grid or GridRaw. It seems to no work.

[@FloWritesCode]

It works just fine in my little test app. What does your setup look like? NavigationStack(path: $path) { Grid { GridRow { Color.green } GridRow { NavigationLink("Test Link", value: Person.examples[0]) } } .navigationDestination(for: Person.self) { person in Text(person.name) .font(.headline) } } This example works just as expected for me in Xcode 14 Beta 3.

[@CodeWithChris]

Hi there! Can you post your concern on our CodeCrew forum codecrew.codewithchris.com? We have our tech support staff that are ready to help you out! :) - Pat

[@TheSpiralnotizblock]

Will the old NavigationLink in future also be deprecated? Sometimes its better than the new one.

[@CodeWithChris]

NavigationView will still be in use for quite some time, especially for app projects that are still on iOS 15 and below, since NavigationStack is not backwards compatible. In reality, production apps, especially those that have an existing user base can't easily raise the minimum iOS version to the latest one upon release as it would hurt their user metrics. Raising the minimum iOS compatibility would mean dropping a percentage of the user base from using your app. - Pat

[@ColeHowe-el5qg]

Thank you man :) Your videos have been *extremely* helpful for me!! :')

[@CodeWithChris]

Happy to hear that! :) - Pat

[@JasemAlqaseer]

Thanks for the great video. I have a question please. I was able to initialize a subview with a binding property with the previous navigationLink initializer. is it possible to do that with the new navigationDestination? thanks

[@CodeWithChris]

Hi Jasem! You can post your question on our CodeCrew forum and have our team assist you. Just visit this link codecrew.codewithchris.com. - Pat

[@w0mblemania]

This was very useful, thanks.

[@CodeWithChris]

Glad it was! Thanks for watching! :) - Pat

[@GorYeghoyan]

Awesome, thx a lot!

[@CodeWithChris]

Thank you for watching! - Pat

[@dugrut1325]

... clear as MUD!

[@CEdits-47]

mud isn't clear

[@umairkhan4982]

Great explanation

[@thomascole8216]

Very nice! Great job...

[@CodeWithChris]

Thank you very much! - Pat

[@bigmtnstudio]

Thanks!

[@CodeWithChris]

No problem! - Pat

[@CodeWithChris]

Thanks for the Tip @Mark! @AdrienVillez

[@andre.unsal.13]

I'm comprehending this for the most part, but how do I get this paradigm working with custom SwiftUI View types? I don't know how I can just enum my SwiftUI views or make them hashable. Each view uses different observedobjects, and my ios15 code works - not sure how to make it work on ios16. On the hunt right now.

[@CodeWithChris]

Hi Andre! We suggest posting your question on our CodeCrew forum and have our tech support staff assist you. Just visit this link codecrew.codewithchris.com - Pat

[@nikitapatidar8907]

What if I don't want to use list and how can pass data over multiple views.?

[@CodeWithChris]

Hi Nikita! We suggest posting your question on our CodeCrew forum so that our tech support staff can help you. Just visit this link codecrew.codewithchris.com. - Pat

[@YaroslavSherstyuk]

How use presentation Detents together with tabview?

[@CodeWithChris]

We suggest posting your question on our CodeCrew forum codecrew.codewithchris.com. Our tech support staff will help you out! - Pat

Thanks! 🙌🏻

[@CodeWithChris]

No problem! - Pat

[@srome0711]

Great video

[@CodeWithChris]

Glad you enjoyed it! - Pat

[@enoch8835]

THANK U

[@CodeWithChris]

You're welcome! - Pat

[@GoeHybrid]

Well, no backward compatibility, as always. "Thanks" apple. I swear to go, ios development is a joke.

[@CodeWithChris]

SwiftUI is a very young language and we can expect a lot more changes in the future too. Indeed, things are going to be interested in September when all this goes live. @AdrienVillez

[@w0mblemania]

@@CodeWithChris The problem is that SwiftUI isn't very young any more... It was released in 2019, and we're up to SwiftUI 4. And with every release, there are show-stopping problems that force us to go back to UIKit. And everyone has to keep asking "is SwiftUI production-ready?". Apple need to dogfood SwiftUI... the vast majority of their apps aren't using SwiftUI yet they tell us that SwiftUI is the best way to make an app. SwiftUI feels like the future, but we have to work in the here and now.

[@CodeWithChris]

Yes... well, I was comparing it to something like Java, C, or even Objective-C. But yes, working with iOS and SwiftUI is a non stop Learning-Coding-Learning-Coding-Change/Fix-Learning-Coding loop. I do understand your frustration. From my experience, Xcode does a pretty good job to suggest edits and new ways to write a line of code when converting an older project. Not sure if this will be the case. PS: This comment thread will slowly disappear in the abyss of youtube's older comments (well, at leas this is how they are given to use), so I would recommend you to join us in the Forum! codecrew.codewithchris.com/. Come and chat with us and talk SwiftUI with the team!) @AdrienVillez