#stripe

Quick question: Isn't Parse more powerful/scalable now that anyone can out it on there own server? (Besides knowing that the API isn't going to get updated with new things)

prgmmr: there are definitely ups and downs to parse being sunsetted

because it comes with the side effect of parse being open-sourced

I'm not a huge parse fan, personally, just because writing libraries for parse is a bit of a pain

(see also the contortions you have to put stripe-node through before it'll run on parse)

tr12: Okay so my dilemma is that a year ago or so I was starting out into programming and so I looked into Parse because I thought I could just focus on iOS side because it's just me. Anyway now that Parse is shutting down, my questions are I'm pretty much done with my app using Parse, should I launch with Parse? Or should I delay the apps launch and do the

whole backend etc, or should I launch with Parse then see how it goes and then slowly create the backend while the app is live. Thanks.

prgmmr: I mean, the path of least resistance is probably going to be to take the open sourced parse, run it on your own server / heroku / whatever, and go from there