I built a large app using this pattern and found two downsides about it: first of all @Environment objects don’t percolate down when there’s a UIKit component between them, and secondly: VoiceOver navigation gets very confused when it’s in for example a UIKit wrapped bottomsheet and won’t let users leave that context.
Thanks for the feedback Kris - I love to hear from others who've also tried this same approach.
Definitely agree that there are some limitations to this architecture - I've found, in particular, custom image transitions with hero animations can be tough to pull off.
I'm having two issues 1. I don't understand how the homeRoute route is declared, is there a code example? 2. present(navContext: profileNavigation, aniamated: true) not found in Switch case profileRoute. Any help would be greatly appreciated.
I built a large app using this pattern and found two downsides about it: first of all @Environment objects don’t percolate down when there’s a UIKit component between them, and secondly: VoiceOver navigation gets very confused when it’s in for example a UIKit wrapped bottomsheet and won’t let users leave that context.
Thanks for the feedback Kris - I love to hear from others who've also tried this same approach.
Definitely agree that there are some limitations to this architecture - I've found, in particular, custom image transitions with hero animations can be tough to pull off.
I'm having two issues 1. I don't understand how the homeRoute route is declared, is there a code example? 2. present(navContext: profileNavigation, aniamated: true) not found in Switch case profileRoute. Any help would be greatly appreciated.