http://venturebeat.com/2015/08/28/parse-ceo-ilya-sukhar-is-l...
when a venture capatilist leaves the team things are not going good somewhere ;)
Facebook is closing Parse
191–200 of 543 posts
Re: Facebook is closing Parse
#192It will be funny to see all of the abandoned apps that start failing a year from now. Obscure games, utilities, etc. Most people won't be bothered to go through the stress of an App Store review process to update an old free-to-play app that's not even making them revenue. But how many people's morning commutes will be ruined when their old games or news apps fall apart? The price of progress (and of liquidity), I su…
> But how many people's morning commutes will be ruined when their old games or news apps fall apart? The price of progress The "price of progress" is suddenly not being able to play WhackAMole 3000 on your mobile phone on your way to work?
Kinda. I mean, I can dust off my old console and play the games on that any time I want. App Store stuff means built in expiration date. Cloud integration means built in expiration date. Price of progress.
Re: Facebook is closing Parse
#193I haven't worked with Parse, but the announcement reminds me of something I decided to do as much as I can.
We sometimes choose to build features on top of third-party vendors' services, and the reality's that unless that third-party derives decent revenue or primarily provides that service; one shouldn't expect that the service will always be available. Twitter was a good example, Google SEO is another, where people who were relying mostly on search traffic got wiped when algorithms were changed.
It takes longer at times, and seems like reinventing the wheel, but for features that I deem to be very useful to my users, I choose to roll out the relevant underlying detail myself. In most cases there are often already third-party libraries that can help with bootstrapping the features. I'm glad that the parse-server is available so people can run their own local instance though.
Re: Facebook is closing Parse
#194This is exactly why I chose to implement everything myself rather than use a cloud wrapper.
Re: Facebook is closing Parse
#195This 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.…
"This announcement just underscores the importance of having full control over your backend"
I disagree. If using something like this let's you get to market much faster, much cheaper, and find market fit faster/cheaper, then it's worth it. Depending on the need it can take millions of dollars and year(s) of work to then begin working on the actual business objectives.
Re: Facebook is closing Parse
#196I hate to be "that guy", but I use their analytics too, along with in-app push notifications that can be targeted to groups of users. Anyone have experience and recommendations for alternatives that are just as easy to implement in an iOS or OS X app?
Re: Facebook is closing Parse
#197I 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.
Obviously you're not a golfer.
Re: Facebook is closing Parse
#198A 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, but simply because they're exactly in the same case (proprietary,non standard, critical technology, held by a company who don't really care about it for its money service). People won't sign up on firebase anymore, so they will have to shut down quite soon.
4/ Every non core project run by facebook should be looked upon with extra caution now. Yes, that includes occulus. They're clearly not going to sell many devices, and gaming console maker (aka Sony) will have the lion's share of the gaming market. So, expect fb to shut it down in 2 or 3 years if it doesn't get a very large marketshare (the only use case large enough i can think of that is not gaming being porn).
5/ I personnaly would be really hesitant now to run on something like google app engine. I wouldn't be surprised to see google and microsoft moving forward api standardization for core cloud services on a much faster pace. Except amazon, nobody is really safe now.
Re: Facebook is closing Parse
#199I 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.
Nearly 3 ;)
Re: Facebook is closing Parse
#200Either their mobile home page is broken or it only shows this announcement anymore, but what is Parse anyway?