Facebook is closing Parse
291–300 of 543 posts
Re: Facebook is closing Parse
#292Earlier quoted context omitted.
I just created an account on OneSignal: https://onesignal.com/
Free - what's the catch? I don't want to have the same problem all over again. Forget the fine print, the body text is really hard to read superthin gray text on white.
We make revenue from products that help companies with advertising and competitive research. Our push service helps us collect the data necessary to make this work, similar to services like Flurry Analytics. So we're happy to provide it for free. Happy to go into more detail via email: contact@onesignal.com
Re: Facebook is closing Parse
#293Earlier quoted context omitted.
I would not tie myself to a Cloud Platform but use open source stuff like docker which can be moved between Clouds. Btw, There's CloudBoost.io which is an alternative to Parse and is both on Docker (self-hosted) or as a managed solution at CloudBoost.io
Would you mind adding a "Disclaimer: I'm the co-founder of CloudBoost.io"? I've got nothing against you promoting your project when people need alternatives, but it's important that people realize you've got a stake in it. Like so: Disclaimer: I work on Compute Engine, but not Firebase ;).
Disclaimer: I don't like disclaimers. Just write what you believe; unapologetically be you.
Re: Facebook is closing Parse
#294Earlier quoted context omitted.
Would it be possible to open source the Parse Dashboard? Even if it's just the data browser? I really loved that part of Parse.
They have already did that: http://blog.parse.com/announcements/introducing-parse-server...
Re: Facebook is closing Parse
#295A few thought : 1/ parse wasn't a core service for facebook, nor a relevant source of a revenu AND their API wasn't standard. Those points combined made it very risky for people to use it. 2/ since they open sourced their API now, and the service was a paid service, there's a very high probability that someone will very soon create a 100% compatible PAAS. 3/ firebase will be next to shutdown. Not because they suck, b…
I think you're pretty far off the mark when you say that Oculus is at risk if they don't sell enough devices. Of course, we have to go off of what Oculus and FB says, but they are working to create an ecosystem and market for VR experiences and seem to be pushing VR forward wherever they can; look at Oculus Studio and the work they're doing to create interactive movies, as well as the software deals with partners lik…
> VR is a huge opportunity and is likely to be the entertainment medium of the future
Is it? Last time it was 3D. And before that..
Re: Facebook is closing Parse
#296I am happy to see that they're not using any of the insulting language that would land them on http://ourincrediblejourney.tumblr.com/ . FYI, here's the announcement of the acquisition from April 25, 2013: http://blog.parse.com/announcements/the-future-of-parse/ Relevant bits: Q: Will my Parse app be affected in any way? No. Q: Will Parse apps have to use Facebook functionality? No. Q: Will Parse honor my contract? Y…
So that will have been nearly 4 years ago.
Re: Facebook is closing Parse
#297Either their mobile home page is broken or it only shows this announcement anymore, but what is Parse anyway?
https://en.wikipedia.org/wiki/Parse_%28company%29
"...back-end tools for mobile developers that help mobile developers store data in the cloud, manage identity log-ins, handle push notifications and run custom code in the cloud."
AFAICT, it was doing all the mundane work you need to get a modern mobile app up and running. So, developers could concentrate on the business logic of their application and leave the rest to Parse.
Re: Facebook is closing Parse
#298While I'm sure this sucks for a lot of people, I'll be honest the shutdown seems pretty fair. One year notice, detailed migration path with accompanying migration tools, and an open source release of the product itself. I didn't use parse, but this seems like a reasonable way to do it.
Re: Facebook is closing Parse
#299This announcement just underscores the importance of having full control over your backend. Yes, it's more work, but if you're writing apps that seriously depend on backend services, it's simply too much risk to depend on anyone else. Fortunately in this case Facebook offered generous lead time to migrate off Parse.com, but they were not obligated to do so, and other providers might not be so generous in the future.…
No, it just underscores the importance of properly architecting your apps so that they don't directly depend on Parse or others. Keeping that stuff to the periphery of your app will make it much easier to replace when the service either shuts down or you outgrow it.
If you continue to rely on BaaS providers you run the risk of playing perpetual musical chairs as each one shuts down over time. That's not an acceptable level of risk for me, but, to each his own I guess.
Re: Facebook is closing Parse
#300Earlier quoted context omitted.
Luckily, this time. Not all startups who provide a service like this may choose to do the same when they implode.
Also many (the majority?) of Parse users signed up with them so that they wouldn't have to self host anything .