Local Storage Support

[cbaker6]

Primitive Storage

ParseSwift has primitive (key/value) storage by default that automatically saves/updates to a devices Keychain and can be synchronized with users iCloud accounts. All .current() objects are saved to the primitive storage such as: ParseUser.current(), ParseInstallation.current(), ParseVersion.current(), ParseConfig.current(), etc. It has been shown that the max size of a single one of the aforementioned key/values is ~16MB. Note, the content of a ParseFile does not count against the max size as the contents of ParseFile's are stored directly to disk.

Cache

ParseSwift also cache's queries and objects saved to a parse-server. Details about how to configure the cache can be found in the documentation. Similar to Primitive Storage, the content of a ParseFile does not count against the cache as the contents of a ParseFile is stored directly to disk.

Examples of using ParseSwift with Local Storage

• ParseCareKit is a middleware that depends on Parse-Swift and conforms to a protocol which keeps the local CoreData store in sync using vector clocks with a Parse Server in a SwiftUI based sample app. It’s a synchronized distributed database. To get some ideas on how to setup your CoreData store for something like this, I recommend looking at Apple's CareKit (specifically the OCKStore)

  • Note that this is different from the other SDKs on purpose to provide more flexibility to the developer. You can see a discussion about the limitations of the current local storage approach in some of the other SDKs issue 1 and issue2 and why we currently believe a protocol approach would be better

• Offline mode #40 attempted to add a local store and may have some useful approaches for design, though it doesn't follow the protocol approach needed to be merged into ParseSwift

[cbaker6]

@claesjacobsson I answered your question on the Parse-Community discord, but the Parse PMC moderates my answers and blocks many of them. If you have questions about Parse-Swift, I recommend you ask them on this repo. If you want an up-to-date Swift SDK, I recommend you use this one, you can see why here: #7. You can update to 4.16.2 with no breaking changes (See #70 for more info). ParseSwift 5.x+ will require changes to your apps that depend on Parse-Swift.

[claesjacobsson]

Thanks Corey!

Even though I don't know the details behind the two forks of Parse-Swift, I realise it must be frustrating for you with all the hard work you have put into this project. Sorry about that and thanks for all that you have done!

From my own business' perspective I am wondering if I should be worried to rely on Parse-Swift in my apps. From your point of view, where do you see this going?

[cbaker6]

Sorry about that and thanks for all that you have done!

Appreciate you!

From my own business' perspective I am wondering if I should be worried to rely on Parse-Swift in my apps. From your point of view, where do you see this going?

IMO, you can rely on Parse-Swift^OG in this repo as I use it in my apps and plan on maintaining it for the foreseeable future. Since I never relied on anyone from the parse-community for the original Parse-Swift, there's no limitation or info I need from them to improve or add features to the SDK. In addition, I have strong understanding of the server as I'm #17 on the parse-server Contributors list (and I still add bug fixes there when necessary), which means I should understand any server-side feature added in the future and translate that to ParseSwift^OG. Also, ParseSwift^OG is stable and modern with version 5.0.0+, so new features should be easy for me to add, and bug fixes should be straightforward.

When it comes to features, the feature comparison tables in #72 demonstrate why I believe ParseSwift^OG is currently the best of the Parse SDKs and will remain that way. In addition, you can write Cloud-Code with it using ParseServerSwift

Lastly, I'll note that ParseSwift was highlighted in issue 560 of iOS Dev Weekly and even caught the attention of an original Parse Developer on Twitter. I do not take that type of attention for granted and believe ParseSwift^OG can provide a better development experience than frameworks like Firebase and the others that are out there, so it will remain in development.