Parse Lets You Run Custom Code For Your Mobile Apps(techcrunch.com)
techcrunch.com
Parse Lets You Run Custom Code For Your Mobile Apps
http://techcrunch.com/2012/09/11/parse-cloud-code/
5 comments
Can we stop linking all this to TechCrunch and giving them hits? Parse has a blog post about this, so let's link to that instead.
The ability to run server code is so great. It amazes me that they got this far without allowing it. But I guess the mobile app market is so huge that many mobile apps didn't require it.
I'm thinking of using parse for a project I'm releasing soon. If anyone reading this has used them I'd love to hear your review.
A year ago I first used Parse for a fun side project to check out the functionality and reliability of the service. I was amazed at how quickly I was up and running with a cute little iOS app that collected user's answers to polling questions and graphed results.
BUT back then I kept running into things I wanted to do with Parse that were not yet supported. e.g. Users could like certain questions, and I wanted to be able to increment the like value. At the time this could have caused collision issues if multiple users requested the like value and incremented it, so instead I created an object for each like and queried on the number of objects. This, like most other hurdles I've run into while working with Parse for about a year now, has been resolved.
As a front-end dev, Parse has literally changed my outlook on what I can accomplish on my own or with the help of a couple other developers. With the cloud code announcement my mind is already racing with the possibilities this opens up to me.
That being said, it's not the solution for everyone. For bigger projects with complicated backend needs, I'd still go with a custom solution.
BUT back then I kept running into things I wanted to do with Parse that were not yet supported. e.g. Users could like certain questions, and I wanted to be able to increment the like value. At the time this could have caused collision issues if multiple users requested the like value and incremented it, so instead I created an object for each like and queried on the number of objects. This, like most other hurdles I've run into while working with Parse for about a year now, has been resolved.
As a front-end dev, Parse has literally changed my outlook on what I can accomplish on my own or with the help of a couple other developers. With the cloud code announcement my mind is already racing with the possibilities this opens up to me.
That being said, it's not the solution for everyone. For bigger projects with complicated backend needs, I'd still go with a custom solution.
How does this effect the current pricing structure?
why is "YC's Parse" and just not "Parse"?