The big idea behind Parse is that developers shouldn’t have to manage a server in order to write mobile applications. Of course, we can’t dream up every application that people want to write. An important part of our philosophy is to listen closely to developers to figure out what we need to build, so that every application can be freed from servers. By working with our community, we think we’ve made Parse a platform that makes mobile development faster, easier, and more robust than any other way of doing it.
Today, we’re proud to announce our release of the Parse SDK, version 1.0. Parse 1.0 represents the biggest milestone in Parse’s development to date: a rock solid SDK ready to power anything from large, complex applications to a quick weekend project.
You can download Parse 1.0 from the Developer Docs.
Parse 1.0 does have a few minor backward-incompatible changes from Parse 0.x versions, that we’ve made in order to clean up some warts and prepare for future functionality.
objectForKey:in iOS and
get()in Android will now never do a network request, which was rarely the desired behavior. Instead, fetching relations happens as a separate step. See the Relational Data section in the iOS guide and Android guide for more details.
getFirstmethods will now return a descriptive error on failure, instead of returning a null result and a null error.
NSNumber, which was a source of bugs. See the docs for example code.
Several method names were changed to adhere to a consistent style. In iOS,
withError:clauses were renamed to
error:. In Android,
className()accessors were removed in favor of the alternative
We couldn’t build Parse without the tremendously useful feedback from the Parse community. Let us know about your greatest hopes and dreams, what you wish the Parse platform could do for you. Or just if you find a bug. We want to make your life easier.
Thanks for using Parse!