This is correct. I originally created this library for someone who was completely new to iOS and SQL. The documentation and syntax for Core Data was a bit too daunting for him. With this he was able to have his project use local storage with a very small learning curve.
I see, nice. Would it have made more sense to use Core Data under the hood, or do you already do that? That way the user could easily transition to using Core Data at a later date, and keep their data?
Currently it just sits on top of Sqlite. I wanted to keep with the whole 'lightweight' concept. Also, all of the apps I have made have used very basic schemas and using CoreData was a bit more overhead than I needed. I wanted to make a library that was easy to setup and use. Making it easy to transition to core data isn't a bad idea though.
Comments
It is primarily aimed at beginners and projects that need basic local storage that is easy to setup.
I believe Core Data can be backed by SQLite so what does this offer, just ease-of-use?
This is correct. I originally created this library for someone who was completely new to iOS and SQL. The documentation and syntax for Core Data was a bit too daunting for him. With this he was able to have his project use local storage with a very small learning curve.
I see, nice. Would it have made more sense to use Core Data under the hood, or do you already do that? That way the user could easily transition to using Core Data at a later date, and keep their data?
Currently it just sits on top of Sqlite. I wanted to keep with the whole 'lightweight' concept. Also, all of the apps I have made have used very basic schemas and using CoreData was a bit more overhead than I needed. I wanted to make a library that was easy to setup and use. Making it easy to transition to core data isn't a bad idea though.