This adds a whole other dimension to Parse for me. Core Data is useful, but incredibly annoying to deal with at times (migrations etc.), I've been waiting for the Parse guys to replace Core Data, and it looks like they've done it.
Thanks, Parse! You just added the one feature that precluded us from using you in our current project. I think you just landed yourself a spot in v1.1<p>BTW, Parse has the best "Quick Start" I have ever used for an API. Great stuff. A+ for removing any and all friction for a dev to take you on a test drive!
Remarkably good, easy to follow tutorial for those who like me don't know what Parse does: <a href="https://www.parse.com/docs/ios_guide#data" rel="nofollow">https://www.parse.com/docs/ios_guide#data</a>
For simple caching in IOS you can also use property lists:<p><a href="http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/PropertyLists/Introduction/Introduction.html" rel="nofollow">http://developer.apple.com/library/mac/#documentation/Cocoa/...</a><p>It has good examples of how to read and write to local files.<p>Another option is to use Three20's TTURLCache:
<a href="http://api.three20.info/interface_t_t_u_r_l_cache.php" rel="nofollow">http://api.three20.info/interface_t_t_u_r_l_cache.php</a>
I'm excited to try this. I'm trying to build something which is fairly firmly Core Data based right now but I desperately need a way to smartly cache client side because the database is growing too large. Hopefully Parse can help me out.<p>My biggest concern is how these are stored and whether I can trust queries to be cached for very long periods of time (like until the data updates).