No, I'll be using Firebase.com or CloudKit.
There's other options I'm also investigating, but those are my top two choices right now. I got to play around with them a bit this weekend during Apple's iOS App Hackathon that I was mentoring at.
Firebase is looking slick, but I have concerns with support since Google owns it.
As with any technology, these parent companies can decide to stop supporting and close down services that developers use. That makes it challenging as you plan for future changes in APIs or service shutdowns.
I trust Google as much as I trust Facebook now... clearly Firebase has way more support for Swift than Parse ever did (as was evident by my 4 hour live stream), but I've seen Google ditch things just as fast.
The real benefit for beginners was that Parse was a turn-key solution that didn't require you manage the servers.
Firebase or CloudKit or Azure make more sense. I'll have to dig into them in the Chapter 5 lessons with my best practices and recommendations for choosing a backend.
Moving forward I can't recommend a service that doesn't get supported. Bugs are too numerous on supported platforms, even open source doesn't mean you get the same type of support (especially when you have 100,000s of customers). Money needs to be spent to get good service and support, open source only goes so far.
Either you need a team to maintain your own services, or you need to use an established service that has a good track record and bright future.Continuing the discussion from 1 sentence app ideas - Please add 10 ideas: