This was very helpful for me, thanks Karin. I'll have to rewatch it again and start playing with these ideas. It's surprising how tricky navigation in SwiftUI can be.
I am not sure if I would say navigation in SwiftUI is tricky. If I compare it to UIKit it is easier to set-up. What makes the examples in this tutorial more complex, is that I am trying to use it in different ways. It really depends on how the developer defines the state and architecture of the app. The other advantage that I forgot to mention is that a more flexible design allows to iterate and change the app flow a lot faster. This is great for prototyping and testing new features.
Thanks Karin for investing your time and creating great content - you're a blessing. I've taken both of your Udemy courses as well. You go into depth about how things work which helps my understanding. So I guess this is just a note of encouragement.
Well said sometimes navigation is a puzzle!! Thank you so much for this video. It really saved my life because I was getting quite confused between Navigation on iPad and iPhone. Also I finally understood how navigationLinks are properly used!
This changes my mind. I think Navigation in SwiftUI it is a completely a mess. But this solution makes sense. I don't know if I only use a one instance of State Manager or create a more generic State Manager. Or I'm starting think in the imperative way 😱. Create content congratulations and thank you.
I am using only one StateManager. I prefer a simple approach. There is also the composable architecture from PointFree github.com/pointfreeco/swift-composable-architecture
Brilliant and thank you - but you shouldn't have had to do the second of half of the video showing how to do work arounds for Apple's work in progress. Sincerely grateful.
Karin great content as always!, I've learned a lot from you. One question, how do you navigate on views from a menu located in the upper right position in the toolbar?
Hi Karin. First of all it's great video, I really like a lot the idea with State Manager. although i have one problem. I have run your code and after calling emojiView from firstDetailView the emojiView loades two times. Kind of: firstView->dietailFirstView->emojiView and the app automaticaly go back to detailFirstView->emojiView. I'm confused now, can't find the reason.
great video.. i have questions: how do you combine this wth MVVM, pass data to next view? and also is it possible to not create new view in the original view?
I am running this on ios15. Everything works fine until I use the StateManager. Then when I select a detailItem, the EmojiItem destination transitions twice. Any idea how to fix this?
Again the automatic subtitles are generated in German in several of the new videos. If you can force them into English, it is appreciated. Greetings and thanks for the work you do.
Sorry, UA-cam drives me crazy. I have my default settings to English, which should autogenerate captions in English. But it seems to have a bug. Next time I have to manually check the language. Unfortunately, it does not autogenerate captions after the first upload. So i cannot easily add English for the existing videos. I will try to pay more attention to this.
This is extremely timely, I literaly started converted my projects over to use what I called a ViewManager. Thank you. One question, when you bounce back to the root view directly is there anyway to prevent the middle view from showing. Be right back with a time index
I have tried to find a way to go back to the rootview without seeing all the views in between. I did not succeed. This is one of the bugs in SwiftUI. I also forgot to mention that this can behaviour differently if I run it multiple times or on different iOS versions. Even big changes during iOS 14 updates. I am really hoping they are going to fix this soon and add more customisation.
I realy cant stop myself to not curse when i see SwiftUI's absolutely terrible navigation system. How can even it is possible to Flutter can clear stacks while navigating and SwiftUI cant as native framework.
Special thanks for showing how to handle navigation on iPhone and iPad
That's more than excellent!! I really appreciate the time and the effort 🙌
This was very helpful for me, thanks Karin. I'll have to rewatch it again and start playing with these ideas. It's surprising how tricky navigation in SwiftUI can be.
I am not sure if I would say navigation in SwiftUI is tricky. If I compare it to UIKit it is easier to set-up. What makes the examples in this tutorial more complex, is that I am trying to use it in different ways.
It really depends on how the developer defines the state and architecture of the app.
The other advantage that I forgot to mention is that a more flexible design allows to iterate and change the app flow a lot faster. This is great for prototyping and testing new features.
Thanks Karin for investing your time and creating great content - you're a blessing. I've taken both of your Udemy courses as well. You go into depth about how things work which helps my understanding. So I guess this is just a note of encouragement.
As UIKit developer I'm getting brain damage watching state-based navigation :D
Awesome video.
😂same here I'm like "no way"
Well said sometimes navigation is a puzzle!! Thank you so much for this video. It really saved my life because I was getting quite confused between Navigation on iPad and iPhone. Also I finally understood how navigationLinks are properly used!
Wonderful video, thank you! I came here mainly for the iPad section at the end, but I found the whole video very helpful.
You just simply AMAZING!!! PERIOD
This changes my mind. I think Navigation in SwiftUI it is a completely a mess. But this solution makes sense. I don't know if I only use a one instance of State Manager or create a more generic State Manager. Or I'm starting think in the imperative way 😱.
Create content congratulations and thank you.
I am using only one StateManager. I prefer a simple approach.
There is also the composable architecture from PointFree github.com/pointfreeco/swift-composable-architecture
your voice motivates me
Great video Karin! I just found you, and this has helped a lot
great stuff, as usual 💪 just a small note - presentationMode environment value is deprecated, now you can grab and use dismiss action instead
Great video! Thank you so much!
You must have 700 000 followers, thanks for the video!
What a great content! Thank you!
Excellent as always, thanks a lot.
Very nice!! thanks for the video
thank you so much for these informative tutorials!
Brilliant and thank you - but you shouldn't have had to do the second of half of the video showing how to do work arounds for Apple's work in progress. Sincerely grateful.
Thanks Pat.
Awesome stuff thank you
Thanks you so much!
Nice Explanation: But can you please do a video on how to do an HTTP post request using SwiftUI with Combine?
This is great! Thank you so much. Can you also do one for custom navigation with custom transitions?
Great video! I have yet to find a way to customize the navigation bar to my liking. Would be interested to know how you would approach it?
Karin great content as always!, I've learned a lot from you.
One question, how do you navigate on views from a menu located in the upper right position in the toolbar?
Hi Karin. First of all it's great video, I really like a lot the idea with State Manager. although i have one problem. I have run your code and after calling emojiView from firstDetailView the emojiView loades two times.
Kind of: firstView->dietailFirstView->emojiView and the app automaticaly go back to detailFirstView->emojiView. I'm confused now, can't find the reason.
Love u! ♥️
great video..
i have questions:
how do you combine this wth MVVM, pass data to next view?
and also is it possible to not create new view in the original view?
I am running this on ios15. Everything works fine until I use the StateManager. Then when I select a detailItem, the EmojiItem destination transitions twice. Any idea how to fix this?
I have the same problem when pushing the aNavigationLink. Xcode is asking me to file a bug.
I’m also experiencing this bug
The solution is to add .isDetailLink(false) to FirsTabView's NavigationLink
@@jacekdogiel8747 Great spot Jacek. Thank you.
@22:52 Paradigm shift for those of us with UIKit brains.
The time index is at about 40:55. Thanks
Again the automatic subtitles are generated in German in several of the new videos. If you can force them into English, it is appreciated. Greetings and thanks for the work you do.
Sorry, UA-cam drives me crazy. I have my default settings to English, which should autogenerate captions in English. But it seems to have a bug. Next time I have to manually check the language.
Unfortunately, it does not autogenerate captions after the first upload. So i cannot easily add English for the existing videos. I will try to pay more attention to this.
Unfortunally this does not work anymore 20:43
How to update environment object from view model?
Setting the selectedEmoji = nil @ 21:46 doesn't work for me, it doesn't navigate back. I'm sure I wrote the same exact code. Is that broken on iOS 15?
This does not work for me using the SwiftUI app preview but it does work when using the device simulator
Thanks!
This is extremely timely, I literaly started converted my projects over to use what I called a ViewManager. Thank you. One question, when you bounce back to the root view directly is there anyway to prevent the middle view from showing. Be right back with a time index
I have tried to find a way to go back to the rootview without seeing all the views in between. I did not succeed. This is one of the bugs in SwiftUI. I also forgot to mention that this can behaviour differently if I run it multiple times or on different iOS versions. Even big changes during iOS 14 updates. I am really hoping they are going to fix this soon and add more customisation.
This is great. Thank you so much. Also - what is your cat's name? :D
I realy cant stop myself to not curse when i see SwiftUI's absolutely terrible navigation system. How can even it is possible to Flutter can clear stacks while navigating and SwiftUI cant as native framework.