clean-architecture

a dismissible view is a presented view that Navigator knows how to dismiss .

For a good code design it's very important to use proper abstractions because they make our code loosely coupled . That means that different componenets of our code can be replaced with alternative implementations without affecting other components. When our code is loosely coupled it becomes easier to test, easier to extend, easier to reuse,... See more

Keep in mind that dismissal is largely imperative and fragile. Like manually popping views off the navigation path, it depends on an assumption of how the app is constructed and what views have been pushed and presented.

That’s not much of a problem if you’re coming at it from the application root side during a deep link. But it can be one if you’re... See more

They all have the same objective, which is the separation of concerns

Source code dependencies always point inwards. As you move inwards the level of abstraction increases. The outermost circle is low level concrete detail. As you move inwards the software grows more abstract, and encapsulates higher level policies. The inner most circle is the most general.

Loosely coupled code is the main goal of Dependency Injection. It enables us to write loosely coupled code.

The concentric circles represent different areas of software. In general, the further in you go, the higher level the software becomes. The outer circles are mechanisms. The inner circles are policies.

Conforming to these simple rules is not hard, and will save you a lot of headaches going forward. By separating the software into layers, and conforming to The Dependency Rule , you will create a system that is intrinsically testable, with all the benefits that implies.