3 ms·
This is good news for me. File storage and push messaging are particularly nice. As a user of the Firebase iOS SDK, I was wondering why the SDK was getting so
by nihonde 10y ago
This is good news for me. File storage and push messaging are particularly nice.
As a user of the Firebase iOS SDK, I was wondering why the SDK was getting so stale. The Quickstart guide used deprecated Swift, didn't offer Carthage support, etc.
I looked at the new docs, and I guess they ditched the old Quickstart format in favor of a bunch of examples. At least the code seems to be up to date, which is somewhat encouraging. I still wish for Carthage support, though.
I see a lot of people worrying about reliance on proprietary BaaS. I had services running on Parse when it announced the shutdown, and it really wasn't that hard to migrate. Firebase should be even easier to leave if necessary, since it's basically just a NoSQL data model. If you abstract your queries and avoid some bells and whistles, you can keep everything in one place for a relatively painless move that hopefully will never become necessary.
- asciimike 10y agoFirebase iOS engineer here: First off, I'm glad you like the new feature additions. We'd love to hear your feedback on Storage and FCM :) Secondly, I'd love Carthage support as well, but there are a few things (built into Carthage) that prevent us from adding this: 1. Carthage requires iOS 8+ (dynamic frameworks only). Firebase supports 7+, and we build static "frameworks", so we'd lose that (which is still relevant in a lot of our developers). 2. Carthage is designed for open source (git based origins only), and while we'd love to get there, we currently ship everything as a pre-built framework.
- nihonde 10y agoUnderstood. Dependency management for iOS is generally pretty terrible, in my experience. I suppose Apple will step in soon, and I hope they do a nice job of it. Anyway, I continue to use (and enjoy using) Firebase for iOS and web.