(Swift + CloudKit) or (SwiftUi + Core Data + CloudKit)

Question

Misaiah OP

Created Jun ’21

Replies 3

Boosts 0

Views 1.4k

Participants 4

Hello everyone!

Im new to SwiftUI and I have been trying to pinpoint the best approach when sending and receiving data using CloudKit.

Is Core Data absolutely necessary to use when building an app with SwiftUI and CloudKit? I've read that Core Data is falling off, which is why I'm questionable on spending time learning it.

Couldn't I simply use SwiftUI and CloudKit without the use of anything else?

I do know that Core Data is NOT necessary when using CloudKit while writing Objective C, but I am wanting to stick solely with Swift as I have been told that Obj C is falling off too.

Thanks for the help!

Boost

Answer 1

deeje OP

Jun ’21

CoreData is definitely not "falling off" :-) Use SwiftUI+CoreData and sync with CloudKit, using either NSPersistentCloudKitContainer, an open-source sync engine like CloudCore, or a third-party sync engine like Ensembles.io

0

Answer 2

iturrajoel OP

Jun ’21

It depends in so many factors, such as how many records you will have, if you need to be able to work offline, and so on.

I have an App (private) that shared a large number of records using CloudKit and a local cache with coredata. Now I'm dividing that App in multiple Apps and I thing I will use a mix between full synchronize tables and cache tables, all sharing the same record zone.

I would recommend that you start using only CloudKit, then you can start adding coredata for cache, if you realize that you need it.

0

Answer 3

bhagyash OP

Jul ’21

https://developer.apple.com/documentation/cloudkit/determining_if_cloudkit_is_right_for_your_app

TLDR - CoreData + CK is great for a single user to sync across his devices, it's incredibly easy you can practically ignore the CK part CK only if you want features where the user shares his data with others via his private DB, manage local caches, etc. This is harder.

0