Comment on Back to the Mac: Parse Adds OS X SupportComments−holgersindbaek13yParse sounds awesome. I'm learning iOS development atm... I definitely need to look into this.If you are to integrate it with a web app (like Instagram also is a webapp now), would you still use parse then? How would that work out?−HectorRamos13yYou can use the JavaScript SDK[1] to build a webapp companion quite easily. This is how we implemented the mobile webapp version of our Anypic app[2].Parse also has a REST API[3] which can be used from your web application backend of choice.[1]: https://parse.com/docs/js_guide [2]: https://anypic.org [3]: https://parse.com/docs/rest−holgersindbaek13yNice. Sounds like the REST way would be best, doesn't it? If you are using Rails at least.−adelevie13yCheck out https://github.com/adelevie/parse-ruby-client and https://github.com/adelevie/parse_resource.Also, with properly-configured ACLs, you should be fine using the JS SDK client-side with a Rails backend.
Comments
Parse sounds awesome. I'm learning iOS development atm... I definitely need to look into this.
If you are to integrate it with a web app (like Instagram also is a webapp now), would you still use parse then? How would that work out?
You can use the JavaScript SDK[1] to build a webapp companion quite easily. This is how we implemented the mobile webapp version of our Anypic app[2].
Parse also has a REST API[3] which can be used from your web application backend of choice.
[1]: https://parse.com/docs/js_guide [2]: https://anypic.org [3]: https://parse.com/docs/rest
Nice. Sounds like the REST way would be best, doesn't it? If you are using Rails at least.
Check out https://github.com/adelevie/parse-ruby-client and https://github.com/adelevie/parse_resource.
Also, with properly-configured ACLs, you should be fine using the JS SDK client-side with a Rails backend.