211–220 of 543 posts
I'm building on top of Firebase at the moment, and this is exactly the sort of thing I'm afraid of.
Google is 100% behind us, and we're continuing to make big investments in the platform. If you have concerns, feel free to ask me questions on twitter: twitter.com/startupandrew
It was fairly painless getting DreamFactory setup.
I give props to Facebook for giving such a long notice though. That should be more than enough time for app developers to switch.
While 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.
Oh definitely. This is a fine example of how to do a service shutdown. Sadly, I await the comments from unprepared customers next year. If you make apps and use any sort of {P,B,S,I,}aaS, do you yourself a favor and follow/subscribe/whatever to their news/release channels.
http://geekestateblog.com/monitoring-microvendors/
It's really important as people build apps (and business value) through composition of smaller services rather than composition of code that they become aware of these external dependencies. And not just at build time, but during the operation of these apps/business processes.
Earlier quoted context omitted.
It's a BA came through and said "Oh, they're not making a billion dollars for us yet? Let's get rid of them!"
BA?
https://en.wikipedia.org/wiki/Apple_Inc._litigation#Libel_di...
wow. A year ago when I rewrote my startup's product in AngularJS I was on the fence between Firebase and Parse. Built prototypes against both and ended up going with Firebase for a few reasons - 1: price, 2: owned by Google and not FB and 3: the whole 3 way data binding thing. Awesome to see them releasing code for the backend but I'm finding this trend really disturbing - relying on 3rd party services for everything…
I want to help put your mind at ease. Google is 100% behind us. If you have specific concerns, please ping me on Twitter: @startupandrew
This 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.
Fixes for Parse bugs were usually not forthcoming from the Parse team---and when things were fixed, more often than not the fix was reverted within a week because it caused something even worse.
For the first six months of our time using them, Parse would only report downtime post facto and backdated by a day. “F@#$k Parse” was perhaps the most frequently uttered phrase among all of us in our douchebag Mission district headquarters. What a life.
All the time, push notifications inexplicably stopped working for hours at a time---we were running a daily sales app, and this really killed us. It ruined dozens of auctions and pissed off tons of our users. But what's even worse? Parse made my life a living hell for a year, and I'm glad they're gone.
While 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.
I 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?
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.
I just created an account on OneSignal: https://onesignal.com/