If you 1) weren’t depending on the iOS Objective-C SDK to handle local storage for you and not using saveEventually
or anything that ends in ...Eventualy
or 2) Plan on handling local storage yourself (CoreData or something else) I strongly recommend using Parse-Swift as excluding what I mentioned above, it does everything the iOS SDK does and more. More query abilities, more features (i.e. support for certificate pinning), and is ~ parity with the JS SDK. In addition, Parse-Swift is designed for SwiftUI. Any method ending in Publisher
uses Combine
. In addition, LiveQuery subscriptions in Parse-Swift can be used as SwiftUI ViewModels out-of-the-box.
If you depend on Parse to handle local storage for you or want something that’s been battle tested, you should use the iOS SDK.
Edit: If you need to support older devices (which it doesn’t sound like you do because you mentioned SwiftUI), you should use the iOS SDK. Parse Swift is for .iOS(.v12), .macOS(.v10_13), .tvOS(.v12), .watchOS(.v5), Linux
and there’s a current open PR to run on Android
.
Edit: Parse-Swift should essentially be able run on Windows and CentOS as well.
There’s a decent differential in the amount of features Parse-Swift has over iOS SDK and my guess is that differential will continue growing over time.