swift-dependencies VS Puddles

Check out www.pointfree.co www.swiftystack.com and www.mobilesystemdesign.com

I’d sincerely recommend the video series and associated repositories on https://www.pointfree.co

Now, with swift-dependencies from PointFree, you get both the ease of reaching out to a singleton with the benefit of easy overriding for unit tests.

I recommend you watch the www.pointfree.co website to have more details on TCA basics

Look into Dependencies from PointFree which definitely allows you to share instances of dependencies.

You'll find more information and details in the "Get Started" section of the repository's readme. And if you want to see it used inside an app, have a look at Scrumdinger, which is a re-implementation of Apple's SwiftUI tutorial app with an app architecture I'm currently working on (the guys from pointfree had the awesome idea to use that example app and re-implement it using different techniques).

Very elaborate: https://github.com/pointfreeco/swift-dependencies A more broad explanation of all types, from not injecting at all until the fancy framework one: https://betterprogramming.pub/six-or-so-flavors-of-dependency-injection-in-swift-cd3d72651662

At a minimum, Composable Architecture, and now Dependencies from Point-Free.

I have built/designed an app architecture for SwiftUI apps with a focus on using as many native mechanisms and patterns as possible, while only adding abstractions and custom types when absolutely necessary. I call it Puddles.

You'll find more information and details in the "Get Started" section of the repository's readme. And if you want to see it used inside an app, have a look at Scrumdinger, which is a re-implementation of Apple's SwiftUI tutorial app with an app architecture I'm currently working on (the guys from pointfree had the awesome idea to use that example app and re-implement it using different techniques).