Any Dependency Injection container which does not support named services out of the box therefore cannot and will not be implemented officially by the Prism team. This is what allows Prism to register your Page for navigation and then resolve it later based on the Uri segment like MyMasterDetailPage/NavigationPage/ViewA. It is also important to consider that Prism has a hard requirement on the use of named service registrations. As a result, we must instead decide whether for memory management and other business requirements our services are best suited as a single instance that will be reused throughout our application or whether we will create a new instance each time it is requested and then allow the Garbage Collector to free up the memory when we are done with it. Unlike the web environment in which many of your services are scoped around the User Request, for Desktop and Mobile applications we are dealing with a single user.

It is important to understand that Prism has no use, and no implementations for Scoped Services.

For those who may be familiar with ASP.NET Core you may be familiar with 3 basic types of dependency registrations: Transients, Singletons, and Scoped Services.

For android instal NCH Prism Plus 10.28