SnapKit VS Swinject

I’ve been using Xcode for the last 13 years or so, and my advice is - us whatever is comfortable and makes sense to you. I use all 3: code*, storyboard and interface builder (xib). They all have their strengths and weaknesses. Storyboards are nice for quick simple screens with table/collection views and cell templates, but sucks when working in a team (merge conflicts on xml files is not fun). Interface builder has the advantage of being really quick for standalone viewcontrollers and views (after some code that takes away the boilerplate part of loading views from nibs) and minimized the git issues. And code is fun when you’re using anchors and frameworks like snapkit (https://github.com/SnapKit/SnapKit) but even when I was doing visual constrains using strings it was fine. Anyway, just try to learn a bit of everything and see what resonates with you. There are no right answers, just preferences.

If you need to use Auto Layout, I recommend using a wrapper SDK like SnapKit https://github.com/SnapKit/SnapKit that is less verbose and less error-prone and assigns translatesAutoResizingMaskIntoConstraints and isActive automatically.

With a library like SnapKit, you can still have the terse, declarative coding style of UIKit. Hell, I once wrote my own poor-man's version of SnapKit on a whim because writing out constraint code manually got tedious.

SnapKit (19k⭐️) has been providing almost the same thing for years. It is already a standard for many companies.

With something like SnapKit (I actually rolled my own poor man's version in like 10 minutes, before learning that SnapKit existed), SwiftUI no longer appeals to me because of it's declarative-style DSL.

SnapKit - Autolayout DSL for iOS & OS X

This. And if you want to learn AutoLayout without the verbosity/complexity of Apple's own APIs, I would look into using SnapKit.

SnapKit - A Swift Autolayout DSL. Language: Swift.

DI is a concept which makes a class independent of its dependency management. It achieves that by decoupling the usage of an object from its creation. This helps you to follow SOLID’s dependency inversion and single responsibility principles. To achieve this in Swift one of the most appreciated library is Swinject. This library not only provides DI but also have many other features like:-

Swinject - Dependency injection framework for Swift. Language: Swift.

We use Swinject which is probably quite similar https://github.com/Swinject/Swinject

So, how do we fix this? There is a cleaner solution. By using a dependency injection framework, such as Swinject we can create a base module that we might call the DI module.