You sound like somebody who feels comfortable handling security, but for boostrapped and/or a self-funded or even small funded startups, that's extra money that goes to plug a major whole that didn't exist with Parse because they made user authentication, permissions, and security simple.
I'm no security expert. So now instead of concentrating on growing the user base, gaining traction and making the best experience possible for our users, that means finding, interviewing, and hiring more people to handle back-end security which takes a lot of time out of improving the product.
How time consuming on a hours per day would it be to stay on top of handling security on your own? How many engineers would it take and at what cost per engineer?
I use Google Analytics, Flurry Analytics, Facebook Analytics and Fabric all with custom events. Fabric is great for real-time. Mixpanel seems to be extremely costly depending on what type of app or game you have.
For broadcast push notifications, I use PushWoosh. They have a lot of features that Parse Push doesn't for broadcast notifications.
As for the in-app client-based push notification triggered by liking or commenting on a post or profile, I have no idea how to replace that without Parse. Hopefully they'll included some sort of guide to help with that migration.
What about push notifications and Parse Config? Social apps that triggered push notifications now loose that functionality when moving to Parse Server, right?
Also what about security? One of the beautiful things about Parse was not having to worry about servers and the security of back-end because you knew Parse was on top of it.
Remember that you do not need to push a new build for your description changes to get updated. Those do not require approval and will go live soon after you hit save in iTunesConnect.
One thing you could do AND SHOULD DO now is post your disclaimer in your app's description. LIKE RIGHT NOW!! Don't even read the rest of what I've posted. Do not pass go. Just go append your disclaimer to your App Page.
Okay, now that you've done that, good. Second, you need to put up a disclaimer screen or modal that happens on launch or viewDidLoad that requires user to agree to your terms of service/disclaimer/privacy policy in order to use the app. If they don't agree, they can't use the app. Period.
As it is now, I can access your app without seeing any messages or disclaimers on the accuracy of the information.
People can be litigious jackasses and may want to find somebody to blame for their grief or problems. With the false perception that every app makes millions of dollars, make sure you are not a target for lawsuits by at least doing the above steps ASAP.
I'm no security expert. So now instead of concentrating on growing the user base, gaining traction and making the best experience possible for our users, that means finding, interviewing, and hiring more people to handle back-end security which takes a lot of time out of improving the product.
How time consuming on a hours per day would it be to stay on top of handling security on your own? How many engineers would it take and at what cost per engineer?