Seriously, I'd come up with cool features all the time, but have no idea how to get started building the server components they needed. Parse abstracts all that pain behind a few Objective-C methods that work just like all the other frameworks I use each day. I can store arbitrary data to the cloud and construct specific queries to pull it back down – without the mental overhead of learning or maintaining a new stack.
It's a simple idea but it's implemented with enough clarity and flexibility that you can accomplish a lot of neat stuff. Huge cheerleader for this team – I think they've got a lot to offer the many mobile developers who have ambitious projects and limited time/budget for outside server help.
I've read the article, seems like an interesting idea, but I just can't see where the comparison comes from.
The goal of Parse is to make server stuff really easy for mobile development.
The goal of Heroku was to make server stuff really easy for Rails development.
Of course the analogy breaks down once you try to be more specific with what "server stuff" means. ;-)
Parse gives you the comfort of not having to think about architecting a server-side component for your mobile app.
GitHub gives you the comfort of not having to think about hosting your own git repositories.
Doesn't every Software as a Service and Platform as a Service company strive to "give you the comfort of not having to think about" running some piece of software on your own servers? The incessant comparisons to Heroku are just silly now.
1) Unless you're building a mobile client for an existing website, would you really bother with authentication? Can't you just transparently store users with a UDID?
2) Client-side caching is the biggest pain in IOS apps. Network calls are relatively easy. I try to make simple/dumb calls to the backend and just do smart filtering and data manipulation on the front end. Parse doesn't really help here. Do they have integration with core data? They don't even seem to mention it.
3) Some of those testimonials are hilarious, but clearly fake. Why not use real ones?
4) You usually need a server running for a landing page, anyway.
5) No support for storing images or audio. Storing simple strings isn't that useful.
Anyway, just my honest feedback :) Good luck!
P.S. those testimonials are real!
Why has no one provided this product yet? Do the TOS for Android Market and AppStore make this impossible?
(To be clear: The deployment part is the part I want, the part that I don't want to have to fuss with)
I like the look of it!
>ParseQuery query = new ParseQuery("GameScore");
query.whereEqualTo("foo", "bar").whereEqualTo("baz", "biz");
The ability to stack query options like that is very Railsy. I have a feeling that as more Rails developers focus on mobile development, they will take some of the nicer API designs with them into the Java/Obj-C world.
I visited both Kinvey and Parse and the one major difference i can see straightaway is that Parse allows schema less development. From their website:
"For example, you do not need to specify any schemas before pushing data to us. Our data API simply uses a schema-less JSON-like format."
While Kinvey lists "model your data and file requirements" as the first step to using their service.
Of course, both the services are still in beta and post-beta pricing will also be a major differentiator going ahead.
I do agree with @biot though. Pricing needs to be better defined and there needs to be the ability for people with side projects to be able to integrate this without forking over $99 a month.
I feel that the much bigger users would be building their own service instead of using Parse as it would be more economical anyway.
The API is simple and does exactly the sort of things you need it to do. Awesome.
It's closer to Urban Airship than Heroku. Just because they are both YC companies doesn't mean they have to be compared.
I see what you did there :) Are Parse guys day9 fan?
We're working on pricing - stay tuned!
If Parse is "Heroku for Mobile" then StorageRoom, the startup I am working for, is "iCloud for content".
Editors manage content in our flexible service online and data is synchronized or pulled from mobile apps.
Different use-case, but we seem to have found another problem where many devs complain. Existing CMS tools suck at this.
If you have a particular use case in mind, we'd love to hear more about it at email@example.com.
Parse is like an envelope labeled "Instant Server Guy – Just Add Water." If you need your app to be able to create/query/display remote data between users, damn, you've got a huge head-start just by dropping in their code.
Danilo, you are a quote machine ;-)