This is a well-written article, but I'm afraid that it kind of misses the point on how SwiftUI Navigation has changed since the introduction of iOS 16.

You briefly touched on that in the conclusion, and I totally agree that state-of-the-art is a moving target, but I don't think that recommending to people that they should fall back on UIKit as the answer.

In a way, that reinforces what I’ve written about SwifitUI since its introduction. SwiftUI is NOT UIKIt. And continuing to perpetuate and promote imperative-based behaviors will not, in the long run, serve us well.

We're about 2-3 months out from having iOS 17 hit, which then puts iOS 16 at current-minus-one, and which in turns puts iOS 16's new "state" based tools within reach.

So lets see your take on doing the same thing from pure SwiftUI-based perspective.