To be single is fast lane…
Or almost, but if you can use singleton on your design use it as much as you can as it is best in performance respect.
Although if you have a lots of views that can be wasted during the user interactions or navigation lifetime you will not benefit garbage collection features till the user ends the application.
Also you have to think if your application is long running, meaning that user is not going to close it, or close it only once in awhile, this case the application will be hanging on and none of
the resources will be free for other applications till your user closes the application.
You could go around on this by creating a child container and drop the child container when you think it would be necessary to free the resources but then you are back in your initial question
of “to be single or not to be single.”
Hope above helps.