Live data from Hacker News

Facebook is closing Parse

blog.parse.com

101–110 of 543 posts

Re: Facebook is closing Parse

#101

>We’re proud that we’ve been able to help so many of you build great mobile apps, but we need to focus our resources elsewhere. I read this as "our Facebook overlords have decided that our revenue/head can be dramatically increased if redeployed on a different part of the overall company, so they have decided to shut Parse down and move us elsewhere." Which is a perfectly fair business decision but this is really sad…

If resource is the question, then I wonder how come they are sustaining WhatsApp? Its a zero-profit activity, the users chat amongst themselves, what does FB gain from that? I guess the parse resource traffic would be little compared to terabytes flowing through the WhatsApp every day.

you kidding?? Knowing what 200MM people are talking about and being able to display them "relevant" ads based upon it is priceless!!

Re: Facebook is closing Parse

#102
post #59

Currently using Parse for Push notifications (it's simple to send a request to Parse and it handles iOS vs Android issues). Is there any tool out there that has similar functionality? Ie. you register all your users devices there and they simplify the sending of push notifications.

It may be worth checking out Taplytics. We do transactional, behavioral and event-driven pushes (plus, you can A/B test all of it in one place) :)

Disclamer - I work at Taplytics!

Re: Facebook is closing Parse

#103

Odd. The Parse SDK had a new release one month ago : http://techcrunch.com/2015/12/14/parse-launches-sdk-support-... That makes this decision seem very sudden.

It actually makes sense that they would cancel the project after a major release (which they were already working on), especially since they open-sourced the stack.

They didn't open source the overhauled web interface.

Re: Facebook is closing Parse

#104
post #2

Separately, we developed an open-source Parse-compatible API server for Node/Express. https://github.com/ParsePlatform/parse-server This, along with the database migration tools released earlier, allow developers a full migration path to move from Parse hosted data + API to their own infrastructure. Over the weekend, I set up a website & app on a $5 DigitalOcean box running Parse and Mongo locally.

Wow, that is a fantastic move. Much appreciated.

Re: Facebook is closing Parse

#105
post #2

Separately, we developed an open-source Parse-compatible API server for Node/Express. https://github.com/ParsePlatform/parse-server This, along with the database migration tools released earlier, allow developers a full migration path to move from Parse hosted data + API to their own infrastructure. Over the weekend, I set up a website & app on a $5 DigitalOcean box running Parse and Mongo locally.

Awesome, I think a small tutorial on how to migrate an existing app from Parse to DigitalOcean would go a long way!

Re: Facebook is closing Parse

#106
post #2

Separately, we developed an open-source Parse-compatible API server for Node/Express. https://github.com/ParsePlatform/parse-server This, along with the database migration tools released earlier, allow developers a full migration path to move from Parse hosted data + API to their own infrastructure. Over the weekend, I set up a website & app on a $5 DigitalOcean box running Parse and Mongo locally.

[deleted]

Re: Facebook is closing Parse

#108
Hey guys, you can try www.backand.com which gives you anything that parse had to offer and much more. Real time, hosting, DB and server side action is just a bit of what they give you. Oh and the best part, it's free.

Re: Facebook is closing Parse

#109
post #96
post #84

Earlier quoted context omitted.

Appboy, Kahuna, or (shameless plug) mParticle if you want multiple options :)

Urban airship as well I believe. I just remember typically finding Parse the easiest each time I had the opportunity to re-evaluate.

Yep definitely, Urban is a great option.

Re: Facebook is closing Parse

#110
post #76

Interestingly, might've been better to: a) release open source versions and announce pricing increase in the future. b) reduce people using the free 30 transactions / second limit. c) maintain in maintenance mode indefinitely. I just don't get why companies shut down services unless they're folding them into open source projects (like Freebase into Wikidata). Maintenance mode seems cheap to me, but maybe I'm missing…

Keep in mind that this is Facebook, so it's likely they just had better things for those developers to do that would generate the company more revenue. It's not in Facebook's interest to keep a business running that's barely breaking even, especially when they can take the team and put it to use elsewhere within the company. (Not that I know what Parse's financials look like, but I'm guessing they aren't making boatloads of money.)
Post reply on HN