Umm… most of that was continued in SwiftUI Microservices: A modern approach to application architecture in SwiftUI.

There’s a section later in the article about late binding.

In your example your list had a lot of objects but they were in a relatively shallow tree. Be interesting to see what the numbers are in regard to a deeper tree.

Say, some scenario where you based the root view on an optional user record and used that to divide your app into a “log in” section and an “authenticated” section. Then somewhere down the tree in a settings section on a profile page you update the user’s email address.

Would that trigger a major view hierarchy update?