I have the same concerns (although I already have apps using Parse in the wild!):
• Will FB kill off Parse? Seems quite unlikely in the short term, but in the long term?
• Are they going to try and force any integrations with FB?
• Will Parse continue to improve (they've done a lot of this recently!) or will it dwindle as others move faster?
• Data / Privacy - what's going to happen with those going forward? These always are a concern in people's minds when FB comes up.
• Facebook's APIs / Developer Support is SHIT... will this happen to Parse too?
Totally agreed that Parse kicks ass, which is why we bought them; we're looking forward to working with the team to continue to improve it!
As a brand new member of the team, I'm really keen to hear more about how we've failed at our APIs and developer support and what we could do to be way better.
Late last year, I've tried to integrate Facebook into two tiny iOS apps. It sucked, and I'm not going to touch Parse in the future.
One of the few things I needed was an app request dialog. It didn't seem possible from the SDK docs (at least not clearly so), the only way was to use the deprecated global Facebook object:
There was no definitive list of possible values for the dialog name or parameters either. Apparently "message" was being ignored, but only for "feed" dialogs...? Apparently there is a replacement now, but it's still in beta. How am I supposed to tell my clients what is possible (and sustainable) and what isn't?
I have the same concerns (although I already have apps using Parse in the wild!): • Will FB kill off Parse? Seems quite unlikely in the short term, but in the long term? • Are they going to try and force any integrations with FB? • Will Parse continue to improve (they've done a lot of this recently!) or will it dwindle as others move faster? • Data / Privacy - what's going to happen with those going forward? These always are a concern in people's minds when FB comes up. • Facebook's APIs / Developer Support is SHIT... will this happen to Parse too?