You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even if the compared SDK's manage to reach feature parity in the future, they will still lag behind ParseSwiftergonomically because they were all built based on the same Parse architecture from the original open-source days (2015), which IMO is clunky for a modern SDK. The exception is Parse-SDK-Flutter which was built by an indie developer (phillwigins), but I would argue ParseSwift has much better ergonomics, more features, and significantly higher codecov (ParseSwiftOG vs Parse-SDK-Flutter) and testing both vertically and horizontally.
Parse-Swift works with SwiftUI out-of-the-box and is equipped with models and view-models. The others require devs to write additional code for models and view-models
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Below is a growing list of feature comparisons of Parse-SwiftOG (netreconlab) against some of the other popular Parse SDKs from parse-community. Note that Parse-SDK-Android, Parse-SDK-dotNET, and parse-php-sdk are not compared, but they both have similar/less features than
Parse-SDK-iOS-OSX
which is in the comparison tables. Parse-SwiftOG also has significant improvements over parse-community/Parse-Swift as there has been ~25K+ code additions and ~30K+ code deletions between the two.Even if the compared SDK's manage to reach feature parity in the future, they will still lag behind
ParseSwift
ergonomically because they were all built based on the same Parse architecture from the original open-source days (2015), which IMO is clunky for a modern SDK. The exception isParse-SDK-Flutter
which was built by an indie developer (phillwigins), but I would argueParseSwift
has much better ergonomics, more features, and significantly higher codecov (ParseSwiftOG vs Parse-SDK-Flutter) and testing both vertically and horizontally.General
Parse-SDK-iOS-OSX
removed support for Cocoapods and CarthageSendable
)Parse-SDK-iOS-OSX
codecov is configured incorrectly so the actual value is less than the number shownParse Types
Authentication
authData
using key/valuesParse-SDK-iOS-OSX
removed in version 3.0.0Parse-SDK-iOS-OSX
removed in version 3.0.0Query
Query Constraints
LiveQuery Server < 6.3.0
Atomic Operations
Beta Was this translation helpful? Give feedback.
All reactions