411–420 of 543 posts
I would like to see a detailed explanation from Facebook on the business front for closing Parse. Developers would now be skeptical about using any Proprietary service for their backend.
Earlier quoted context omitted.
A few more thoughts: 1. This effectively poisons the well for any other BaaS providers out there. If two of the biggest companies in this space (StackMob and Parse) can get acquired and shut down in less than 5 years, what does that say about the future of the smaller companies in this space? As a developer how could you possibly trust any of these companies going forward, based on this track record? 2. Syncing is no…
This will definitely make me more wary in the future. I considered both Parse and Firebase for my app's backend and even did some early prototypes using each. Parse ended up being closest to what I needed for the basic app features. I would have used Firebase for real time syncing in a multiplayer version but decided to put multiplayer on hold so I could actually just deploy something. I kind of got lucky dodging the…
A 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…
Consider moving to Couchbase Mobile ( http://developer.couchbase.com/mobile ). Why? - Its an open source solution that allows you to build mobile applications that work online and offline. - With Couchbase Lite, you have the full power of a Couchbase database locally on the device. You can create, update, delete, query, sync and much, much more. - Couchbase Sync Gateway gives you everything you need to securely sync…
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.
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.…
A few more thoughts: 1. This effectively poisons the well for any other BaaS providers out there. If two of the biggest companies in this space (StackMob and Parse) can get acquired and shut down in less than 5 years, what does that say about the future of the smaller companies in this space? As a developer how could you possibly trust any of these companies going forward, based on this track record? 2. Syncing is no…
Especially given the fact that the very goal of most VC companies is acquisition.
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.…
Not to be a dick, but some companies seem to care more than others about the developers that rely on their frameworks. Google doesnt seem to care much. Facebook seems to care more. But Microsoft seems to care most. They have not abandoned legacy mfc, visual basic, and win 32 developers even though they probably should have. Granted those are not services but they require maintenance resources nontheless.
On the other hand, Facebook's API changes at a pretty rapid pace and there are few apps older than a couple years that have survived without significant code changes. I've seen API changes that are basically "rewrite your whole app".
Earlier quoted context omitted.
Firebase disagrees with you https://twitter.com/Firebase/status/692845862527995904
To be fair, would they say anything else? Even if Google had plans of shutting them down in 3 months, it's not like they'd come out and say, "Oh, we'll be joining parse next quarter."
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.
It's nice that you've released an open source migration path. I hope somebody else can fill the niche of a fully hosted API-as-a-service. Best wishes.