[dfansteel]

1. Don't have massive VCs by not having massive VCs. That sounds unhelpful, but hear me out... You're asking the VC to do too much. Break that sucker down. Have many, many small classes that do small things. Use libraries for stuff. A VC should be a hub to transit data from the user to a model us MVVC, MVP, MVC... I don't care, every architecture has their acolyte.

2. No. Again not helpful. This is a domain specific problem. I will say I'm waging a now multi-decade war against singletons. Dependency injection is the way to go. For Swift checkout Swinject, it really superpowers your testing.

3. Haven't touched it... yet. My primary projects need to ship and my secondary projects haven't hit the point of UI. Won't until later this year. Then I'll deal with SwiftUI. Combine, however, is my new hawtness and I recommend diving into.