SnapKit VS GRDB.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.

I'm using GRDB , you can use existing pre-populated sqlite DB file. https://github.com/groue/GRDB.swift/wiki/Performance .

Not quite exactly sure what you mean but if its a .sqlite3 file then you can use it with this easy to use library https://github.com/groue/GRDB.swift

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

The other thing is that it could be an overkill for your app if you just need to basically "store an array of 100 objects". Then you could probably consider other solutions like SQLite (with wrappers like GRDB) or plain JSON files.

https://github.com/groue/GRDB.swift#readme https://github.com/groue/GRDB.swift/tree/master/Documentation https://swiftpackageindex.com/groue/grdb.swift/documentation/grdb/

https://github.com/groue/GRDB.swift/blob/master/Documentation/AssociationsBasics.md might be interesting to look at for how it handles relationships between entities.

I recently used GRDB.

Check the performance comparison page. GRDB comes with a convenient and ready-made support for Swift Codable that performs quite well. When needed, it is possible to write less convenient but optimized record types that add very little overhead to SQLite, and perform really well.

Hey all. So I just got done developing an app that does visitation tracking. Basically the user creates an account with email, name, password etc.. the info is then saved to a SQLite database (using GRDB) with a table named "User" and then injected into the next view controller and so on... I plan on allowing the user to store their account in icloud in the future.