MVVM-C with App Dependency Container

I am adopting MVVM-C with App Dependency Container pattern and I’ve faced the following questions:

  • Is it the app dependecy container the responsible to create the app coordinator?

  • As the app container instance is retained on the app delegate, is it possible to have an unowned reference to app container on the app coordinator? (in order to give the coordinator, the ability to create objects with that container)

  • Is a good practice having a container for each coordinator (flow/feature)?

  • As long-lived objects like a store manager or api requester are in the app container, can be injected and retained by other objects as unowned references?

Thank you very much. I love this book

1 Like