Kingfisher VS SnapKit

The 3rd party library I use GRDB SwiftyUserDefaults Kingfisher SwiftDate Popovers

Saving URLs definitely the way to go. Would recommend using a library such as Kingfisher to do the image loading/ caching for you.

I also looked into this github library but wanted to first ask if anyone's had any experience using it.

You can checkout Kingfisher library (it downloads image, and caches it). Usage is fairly simple but I would recomment that you create extension for the UIIMageView, somthing in line like this:

In native iOS, most people use Kingfisher, and i'd love to have something as good as that on our RN app. Perhaps just some pure JS library that you could plug on the existing image component, and that would handle the saving-to-disk and fetching of the image?

Kingfisher - Download and cache images

We are using https://github.com/onevcat/Kingfisher for smooth image loading in collection view. If the image data are not in regular text file, how can we integrate CoreData's blob data with Kingfisher?

Make sure the proper target is selected in the Add to target in the dialog as shown above, then click Add Package button. The package should successfully be added to your project. Now following the same process, this time search for the Kingfisher package using the GitHub URL as the following https://github.com/onevcat/Kingfisher.

Kingfisher - A lightweight, pure-Swift library for downloading and caching images from the web. Language: Swift.

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.