Functional difference, UINavigationController vs Only Storyboard Segue

Question

So the UIKit Framework Reference describes it UINavigationControlleras an efficient way to present data and representations to the user. But I'm curious about the differences in performance and manageability between using UINavigationControllerVS SegueOnly.

There should be certain situations that are better suited to each other. I am completely new to coding, but instinctively I believe that UINavigationControllermore to represent VC, and each of them works a lot, and the user spends a lot of time on each VC equally or that several VCs must work and store data at the same time . And what's Seguemore for Uni-directional VC progression or short-term VC presentations with low data levels. Are any of these assumptions correct?

What is PROS to implement UINavigationController?

Answer 1

. segue . . segues. segues .

A UINavigationController - . , . , ( , , , ). , "" , .

UINavigationController , , UITabBarController UISplitViewController, UIPageViewController. , .

Segues . , , .

, segues. , , .

---

, ?

A

. , . . segue. Segue , , , .

B

, . () () . . root. , , , , . () ( ) . segue A ( A, , segue). segue .

C

( ) . , . , , . viewControllers, , . , , .

---

Segue - , . , segues , ( ), , ).

, . , , , , segues. . . , , , ... , , , .

, segues - , , . , - - , , . " ?" , , , .