NavigationStack != UINavigationController

Did you know that appending an element to the navigation path of the NavigationStack is not equivalent to calling push on a UINavigationController? Let's see the differences together.
If you liked this video, I would appreciate if you hit the like button and subscribe!
Want to learn how you can modularize your iOS Projects? Check out my comprehensive course on iOS Modularization here (discount link):
www.udemy.com/course/scalable...
CHAPTERS
00:00 - Introduction
00:23 - The Behaviour Difference
01:11 - Looking at the Code
02:15 - Potential Bug With Unidirectional Flow
03:53 - Debugging
04:47 - Appending Before Previous Push Completes Problem
05:50 - Closing
- My Links -
Github: www.github.com/emrepun
Linkedin: / emre-havan
Medium: / emrehavan
Twitter: / emrehavan
#swift #swiftlang #iosprogramming

[@suleymanbasaranoglu8642]

Thank you for detailing :) I think SwiftUI case is correct for user experience, I don't want to other pages when I navigate to target page ^_^

[@emrepun]

Hey, yes in some scenarios it is beneficial to show the latest appended view to the user, but sometimes it can be detrimental, like in the example of a unidirectional onboarding flow, where some users might miss some important information :)