Parse launches JavaScript SDK: Parse for Websites • Hacker News Board

Re: Parse launches JavaScript SDK: Parse for Websites

#41

Post by natesm » Wed, May 30, 2012, 6:36 PM UTC

tocomment wrote: post #33

nbclark wrote: post #30

My take on Parse is that they do the grunt work that is necessary with every new project. I am currently building an iPad game on top of parse, and while the pricing is a bit concerning, I figure one of two things will happen: 1) The game takes off and the $200/mo is affordable 2) The game doesn't take off and the 5mil requests is adequate. The lock-in concerns are valid, but right now their API isn't so mature that…

How does parse save you time building your ipad game? Sorry if that's a dumb question. I'm still trying to wrap my head around what it is.

It would probably work pretty well for a game based around creating and sharing levels.

Re: Parse launches JavaScript SDK: Parse for Websites

#42

Post by zomgbbq » Wed, May 30, 2012, 6:38 PM UTC

I sent the Parse guys a tech-support request on Friday morning before Memorial Day weekend. Most places you send emails to are a black hole and I didn't really expect a response until after the holiday weekend, if at all. To my surprise, I had an answer in my inbox by end of day! This is the kind of support I love in a company. I have not stopped telling everyone I know that they need to check out Parse. They're saving me tons of time getting my next app out the door.

Re: Parse launches JavaScript SDK: Parse for Websites

#43

Post by [deleted] » Wed, May 30, 2012, 6:41 PM UTC

zomgbbq wrote: post #42

I sent the Parse guys a tech-support request on Friday morning before Memorial Day weekend. Most places you send emails to are a black hole and I didn't really expect a response until after the holiday weekend, if at all. To my surprise, I had an answer in my inbox by end of day! This is the kind of support I love in a company. I have not stopped telling everyone I know that they need to check out Parse. They're savi…

[deleted]

Re: Parse launches JavaScript SDK: Parse for Websites

#44

Post by nbclark » Wed, May 30, 2012, 6:42 PM UTC

tocomment wrote: post #33

nbclark wrote: post #30

My take on Parse is that they do the grunt work that is necessary with every new project. I am currently building an iPad game on top of parse, and while the pricing is a bit concerning, I figure one of two things will happen: 1) The game takes off and the $200/mo is affordable 2) The game doesn't take off and the 5mil requests is adequate. The lock-in concerns are valid, but right now their API isn't so mature that…

How does parse save you time building your ipad game? Sorry if that's a dumb question. I'm still trying to wrap my head around what it is.

A few things:

1) It makes user management stupid-simple. I can authenticate with Facebook/Twitter/signup easily (not that it's really that hard, but still), and the user info is automatically saved to the cloud.

2) I then use it to store game state, retrieve a list of active games/previous games.

3) Push notifications are really easy. Each client opens a "channel", and the other client sends a push to their opponent's channel after their turn is complete.

I suppose I should clarify that I am building a turn-based iPad game, where the game state needs to be stored between turns.

Re: Parse launches JavaScript SDK: Parse for Websites

#45

Post by [deleted] » Wed, May 30, 2012, 6:43 PM UTC

peripitea wrote: post #27

lacker wrote: post #8

Earlier quoted context omitted.

There are two main types of security. Object-level, and app-level. Each object gets access controls that are similar to ACLs in Unix systems. That provides for the sort of security that separates different users' data from each other. On an app-level, you can also control per-class which operations are usable. For more detail, see: https://parse.com/docs/data#security You should be able use these in combination to se…

I still don't get how I, as a malicious (or curious) user with some form of write permission, would be prevented from doing the equivalent of opening up Firebug console and typing while(true){var p = new Post(); p.save();}

[deleted]

Re: Parse launches JavaScript SDK: Parse for Websites

#46

Post by [deleted] » Wed, May 30, 2012, 6:49 PM UTC

peripitea wrote: post #27

lacker wrote: post #8

Earlier quoted context omitted.

There are two main types of security. Object-level, and app-level. Each object gets access controls that are similar to ACLs in Unix systems. That provides for the sort of security that separates different users' data from each other. On an app-level, you can also control per-class which operations are usable. For more detail, see: https://parse.com/docs/data#security You should be able use these in combination to se…

I still don't get how I, as a malicious (or curious) user with some form of write permission, would be prevented from doing the equivalent of opening up Firebug console and typing while(true){var p = new Post(); p.save();}

[deleted]

Re: Parse launches JavaScript SDK: Parse for Websites

#47

Post by lacker » Wed, May 30, 2012, 6:49 PM UTC

falava wrote: post #40

Comparing the JS guide with the iOS and Android guides I see two absences: 1) Files 2) Facebook and Twitter users May be that it's not possible to upload files or authenticate using OAuth using only the JS SDK, and without having and external server that secures the private keys?

We want to add both of these features. It will just require a slightly different design than the native mobile versions - files because there is no "binary" type in Javascript, and Facebook/Twitter users are different because integrating with other Javascript libraries is slightly less straightforward than integrating with other native libraries. They should both be possible, though, so stay tuned!

Re: Parse launches JavaScript SDK: Parse for Websites

#48

Post by jgannonjr » Wed, May 30, 2012, 6:51 PM UTC

equark wrote: post #37

peripitea wrote: post #27

Earlier quoted context omitted.

I still don't get how I, as a malicious (or curious) user with some form of write permission, would be prevented from doing the equivalent of opening up Firebug console and typing while(true){var p = new Post(); p.save();}

What prevents you from doing this with ajax post on every existing website?

This is true, but at least if you control your own backend you can do some sort of rate limiting on the server side

Re: Parse launches JavaScript SDK: Parse for Websites

#49

Post by nanijoe » Wed, May 30, 2012, 6:51 PM UTC

lopatin wrote: post #34

nanijoe wrote: post #26

Earlier quoted context omitted.

I really wish they charged by something other than API requests..as it stands now, I would not even know a reasonable way to pass on the cost to my users.

Whats wrong with estimating the number of API requests the average user makes and figuring out a price based on that?

How do you do that without first having the users make the API calls, at which point you are already using the service and the estimate is useless..

Re: Parse launches JavaScript SDK: Parse for Websites

#50

Post by lacker » Wed, May 30, 2012, 6:52 PM UTC

pbreit wrote: post #19

I'm still a little confused by what Parse does and when I would use it. It sounds neat for little, proof-of-concept demos but would I consider it for production of something significant? Does this SDK work without the Parse server?

Parse lets you develop apps without writing any server code. For mobile apps and now also web apps, you can just write frontend code. We have a number of large apps in production using Parse - check out the testimonials at http://parse.com - so you could definitely consider it for significant use.