SnapKit VS Realm

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.

Presumably realm in Element for Android. https://realm.io/ "Realm by MongoDB"

See also https://github.com/vector-im/element-android/issues/1025

Looks really cool, I like to make very minimalistic dependency choices for the web apps I work on. Web Components look interesting and it's great to see frameworks that build upon it and provide features that are currently missing from it.

When I landed on the page I remembered another Realm framework I used a lot long time ago. https://realm.io has the same name and the logo looks very similar too. Not sure if it's a problem, just wanted to share. :)

Realm (Open Source but Sync is SaaS)

Realm is a fast, scalable alternative to SQLite with mobile to cloud data sync that makes building real-time, reactive mobile apps easy.

I would focus on Kotlin instead of Java, there's really no point in sticking to Java at this point. And when it comes to databases, some local ones that are pretty easy to get into are Realm and ObjectBox, SQLite can definitely be a bit overwhelming at the beginning.

So yeah, if you don't have a server with API which will store data for you - you should really look into CoreData and Realm

Try Realm.

Just to add to this, there's also Realm and ObjectBox as alternatives.

There is some crossover between the BaaS of Firebase and what MongoDB Atlas is offering if you are developing using Atlas Sync and Realm. Even so, there is a whole lot more you can find in terms of tutorials and community support for Firebase so it is hard to know how many of the Mongo claims are just future bugs for your project vs what people are currently doing with Firebase.