The Story Behind SwiftletModel

Related: SwiftletModel

I've always been frustrated by domain model design and persistence layer implementation when building an iOS application.

Not only it is a disgusting trade-off, but it's usually a very hard-to-reverse decision. Once you pull in the CoreData/Realm/SwiftData/Whatever and build the application around it, the migration to another solution will be an immense cost.

Why would you love to migrate? Well... there might be reasons. But first, let's start with the reasons to pull them in.

For offline-first applications, it's straightforward – there is no option other than spinning up a local database.

How about backend-centric applications that use the backend as the source of truth?

There are options: [[Persistence Layer for Backend-First iOS applications]]