So yeah, this kind of teaching style; showing a bunch of variations on the same theme without dragging the audience through a meaningless app building exercise - you hit the nail smack dab on the head. This is golden, more please ! Thanks for taking the time to study the new API and condense it down into a vid. Very nice Karin!
I thought that adapting new navigation APIs in my app would be a pleasant walk in a park. It couldn't have been further from the truth. The app was crashing and hanging. Navigation links weren't working at all. This video definitely set me on the right path. Thank you so much!
Wow! Karin this was amazing! It was very detailed and you saved me A LOT of time! Thank you! ❤
Рік тому+1
48:26 I burned myself with that lately. The environment object supplies ancestor views. But when you put it on the RootView and then push another view - this view is not part of the RootView, but NavigationStack. So in order to make it work properly, you would have to put it directly under NavigationStack. Screens will always be part of the NavigationStack or NavigationView. Other screens are just View siblings for RootView, not ancestors. Edit: Oh sorry, you figured this out later in the video.
Thank you very much Karin! This is by far the most comprehensive tutorial on NavigationStack if found till today! Did you also try out a TabView with each tab being a NavigationStack having its own path? I wonder what best practise would be in such a design?
Hi Karin, Can you provide an example of LoginView -> (clears stack and push) HomeView ->(push) ListView ->(push) DetailView -> (clear stack and push) LoginView ?
Very good tutorial. Question about the ModelDataManager being put into the environment. Why didn't you add it to the app Entry @Main and all subsequent views are children/kinderen? Is there a problem with that approach? I tried it it and it works fine...maybe it will break somewhere; but not yet. Fingers crossed waiting for your reply.
I'm struggling to figure-out the best option for navigation when I have a mixture of non-value and value based navigation... and there's no tutorials on it. For example, to get to my main settings screen I use traditional destination based navigation links. But deeper in, I'm using value based navigation. It turns-out you cannot used the "dismiss" action with the isPresented navigationDestinations... and everything just becomes more messy that it needed to be.
great video, could you make a tutorial on how instagram accomplishes their custom scale transition in the explore page? i’ve seen it done in UIKit but was unsure of the implementation, or is it only possible in SwiftUI
Thanks Karin, I finally understand view stacking better, just one question, do you to create stacks per tabview or can you it on the highest level of your app? thanks Pierre
Hi Karin Prater, amazing tutorial, actually even better than the apple kitchen one. Can you suggest a simple solution to change the default slide animation? Also to apply to the full stack or only the navlink?
Could we have multiple navigation stacks in a SwiftUI app? Let's say I have a login flow, onboarding flow, and the main app flow. Could I use a navigation stack in the root view of each flow or just have one Navigation stack enum that covers all the flow in the app.
If i start learning ios development in 2024 should i start with SwiftUI or UIKit? And should i even consider native ios development as a career with KMP and React native coming on to the scene.
i have question, can we use viewModels as enums associated type? for example second viewModel that is observable object and sotored in some other object like in stateObject viewModel. that might be second(viewModel:SecondViewModel). can we do that if we can is it right to do that?
hello lady please how to create a pdf report , i mean full report with custom header ( company name, address, phone .. ect ) then report header ( invoice number, date, total, customer .. ect ) finally report rows(item, qty, total .. ect) thank you
So yeah, this kind of teaching style; showing a bunch of variations on the same theme without dragging the audience through a meaningless app building exercise - you hit the nail smack dab on the head. This is golden, more please ! Thanks for taking the time to study the new API and condense it down into a vid. Very nice Karin!
I also found it really helpful than those fast paced tutorials of building an app
I came back after all this time because I still remembered I could find the best SceneStorage explanation here. Thanks again!!
Damn, that last part. You've truly mastered that API
I have challenged myself to learn swiftui in one day and this is the video. Just like a wow😮
Best Swift channel! Thanks for making swift content!🙏
I appreciate that!
thank you so much!!! finally I understand it with navigationPath not even the documentation explain it !!!
THANK YOU ! This was so helpful. I am finally moving to SwiftUI from UI Kit and Navigation has really confused me until now : )
You've just saved the UX of my application, thank you very much!
I thought that adapting new navigation APIs in my app would be a pleasant walk in a park. It couldn't have been further from the truth. The app was crashing and hanging. Navigation links weren't working at all. This video definitely set me on the right path. Thank you so much!
I watch many NavigationStack videos; I still don't understand it. So hope you will make it clear. I'm excited to watch.
Thanks!
Nice video Karin, u got a new subscriptor… go a head!!!
Awesome descriptions. Thank You!
Karin, thank you for video! It helped me a lot! i can knew how can use destination without navigationLinks! 🤗
Great video Karin, congrats and thanks a lot…
Thank you, I’ve spent 40 hours to get understandable for me info. And your describing is awesome and nice. ❤
Great content! This video really helped us out. Well done, THANK YOU! I purchased your courses!!😀
Thank you 😊 Karin for the detail explanation.
Now this is a tutorial. Stellar.
Really really useful and well-made. Thank you!
Glad it was helpful!
You are the best ❤❤❤, this is my fav iOS channel by far !
Wow, thanks!
Wow! Karin this was amazing! It was very detailed and you saved me A LOT of time! Thank you! ❤
48:26 I burned myself with that lately. The environment object supplies ancestor views. But when you put it on the RootView and then push another view - this view is not part of the RootView, but NavigationStack. So in order to make it work properly, you would have to put it directly under NavigationStack. Screens will always be part of the NavigationStack or NavigationView. Other screens are just View siblings for RootView, not ancestors.
Edit: Oh sorry, you figured this out later in the video.
Extrodinairly well explained. Well Done !
Brilliant! Thank you for this great work.
You do an amazing job. Brilliant. Thank you for your videos and tutorial.
Great coverage of this new way of doing things
Glad you think so!
Great explanation. Thank you.
Great videos, liked and subd
1:01:46 you're being polite ;-) I thought the way they did it was crazy!
It always feel a bit strange to critic code from Apple engineers. But it really is too weird.
55:20 : the .navigationTitle is no longer a bug (Xcode v15.3)
Thank you for the Tutorial👍
Thank you very much Karin!
This is by far the most comprehensive tutorial on NavigationStack if found till today!
Did you also try out a TabView with each tab being a NavigationStack having its own path? I wonder what best practise would be in such a design?
Not yet! But this should work because Apple recommends using NavigationStack inside TabView
That was very helpful, thank you!
Thank you! Amazing video. 🤗
Hi Karin,
Can you provide an example of LoginView -> (clears stack and push) HomeView ->(push) ListView ->(push) DetailView -> (clear stack and push) LoginView ?
Thank you! Help me a lot !
Great tutorial. Thanks
Great explanation!
Very happy to hear!
Very good tutorial. Question about the ModelDataManager being put into the environment. Why didn't you add it to the app Entry @Main and all subsequent views are children/kinderen? Is there a problem with that approach? I tried it it and it works fine...maybe it will break somewhere; but not yet. Fingers crossed waiting for your reply.
I'm struggling to figure-out the best option for navigation when I have a mixture of non-value and value based navigation... and there's no tutorials on it.
For example, to get to my main settings screen I use traditional destination based navigation links. But deeper in, I'm using value based navigation. It turns-out you cannot used the "dismiss" action with the isPresented navigationDestinations... and everything just becomes more messy that it needed to be.
great video, could you make a tutorial on how instagram accomplishes their custom scale transition in the explore page? i’ve seen it done in UIKit but was unsure of the implementation, or is it only possible in SwiftUI
Thanks Karin, I finally understand view stacking better, just one question, do you to create stacks per tabview or can you it on the highest level of your app?
thanks Pierre
Hi Karin Prater, amazing tutorial, actually even better than the apple kitchen one. Can you suggest a simple solution to change the default slide animation? Also to apply to the full stack or only the navlink?
Thanks for sharing 😊… when you make a new course?
Could we have multiple navigation stacks in a SwiftUI app? Let's say I have a login flow, onboarding flow, and the main app flow. Could I use a navigation stack in the root view of each flow or just have one Navigation stack enum that covers all the flow in the app.
Thanks for this. Are you able to add a background color behind the entire list? I’ve tried everything and it won’t work for me
If i start learning ios development in 2024 should i start with SwiftUI or UIKit?
And should i even consider native ios development as a career with KMP and React native coming on to the scene.
So if my minimum deployment target is iOS 15 Should I go for uikit instead of swift ui coz a good overall navigation in the app?
Hey, can you make a video about adding Images into our project like PhotosPicker?
cool...thanks.
i have question, can we use viewModels as enums associated type? for example second viewModel that is observable object and sotored in some other object like in stateObject viewModel. that might be second(viewModel:SecondViewModel). can we do that if we can is it right to do that?
Have you managed to adapt this new navigation API with the Coordinator Pattern?
Are you officially working in some company or you are a freelancer?
the meat of the video was good... but you really went down a rabbit hole!
you are so smart, can you marry me?
hello lady
please how to create a pdf report , i mean full report with custom header ( company name, address, phone .. ect ) then report header ( invoice number, date, total, customer .. ect )
finally report rows(item, qty, total .. ect)
thank you
Finally 🎉
Thank you :)