{"id":36020,"date":"2022-05-31T15:17:26","date_gmt":"2022-05-31T19:17:26","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=36020"},"modified":"2022-05-31T15:17:26","modified_gmt":"2022-05-31T19:17:26","slug":"parse-swift-sdk","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/05\/31\/parse-swift-sdk\/","title":{"rendered":"Parse Swift SDK"},"content":{"rendered":"

Dave Verwer<\/a>:<\/p>\n

Parse lasted longer than their major competitor, Stackmob, who was acquired<\/a> and then shuttered<\/a> just a few months later. But eventually, in 2017, Facebook turned off the hosted Parse servers.<\/p>

They did open-source the platform<\/a> as they closed it down, partially due to the huge number (600,000, according to this article<\/a>) of apps they’d disrupt without a migration path. I was vaguely aware that the open-source project was still around but I hadn’t paid much attention until I spotted this package<\/a> pop up in the Swift Package Index<\/a> RSS feeds this week.<\/p>

[…]<\/p>

Why am I writing about this? Well, it has always been risky to base an app on another company’s back-end server. Yes, it can save a lot of time, but you’re always at the mercy of another company’s business decision, and their priorities almost certainly don’t match yours. Maybe the platform you pick will shut down, fundamentally change its pricing, or make another decision that doesn’t work for you. Your options are limited as these frameworks live at the heart of your app. The Parse platform<\/a> is now free of many of those problems. As it is open-source, it’s almost impossible to shut down, and being self-hosted, you’re in control of pricing.<\/p><\/blockquote>\n\n

Previously:<\/p>\n