Latest Issue Archives Sponsorship
iOS Dev Weekly
Search

Your search for firebase returned 9 results

  • News

    Is Apple Banning Free Analytics SDKs?

    There are some great points raised in this post from Allen Pike, but this sentence from his conclusion should stop you in your tracks if you use Firebase:

    all iOS apps should be prepared to migrate off of the Google Analytics, Firebase, Facebook, and Flurry SDKs, potentially on very short notice

    I intentionally stopped linking to anything related to Firebase (and similar services) part-way through 2018 as, in my opinion, putting a third-party library at the core of your app was too big a risk. Alan's article isn't specifically about Firebase, but the dependencies you embed in your app, and the privacy policies that come with it, should be a part of your decision process. It's one thing to need to switch out your analytics provider on short notice, but I can't imagine trying to replace Firebase in a non-trivial app.

    For full disclosure, Firebase sponsored this newsletter back in 2014.

    Issue 494 • Feb 12th 2021

  • Sponsored Link

    Store & Sync Realtime Data with Firebase

    Using Firebase's powerful iOS SDK, you can easily build realtime apps without worrying about networking, scaling, or writing complicated server code. See how it works and start developing instantly.

    Issue 135 • Feb 28th 2014

  • Sponsored Link

    New: Deep link users to the right place inside your app, even after app install

    Firebase Dynamic Links are smart URLs that allow you to send existing and potential users to any location within your iOS and Android apps, even if they don’t have it currently installed. Once installed, users will be automatically sent to the original link they clicked on and see the content they we’re looking for. Dynamic Links are free forever for any scale, and are already in use by many of the apps you use daily.

    Issue 267 • Sep 9th 2016

  • News

    Introducing Cloud Firestore

    Since Parse died (or did it?) the market for cloud hosted data store services has still been evolving, but at a much slower pace than before. There's Realm and of course there are the big players like Azure and Firebase. So what is Cloud Firestore from Google then? Well... it's kinda like the Firebase Realtime Database, but different... Here's a detailed comparison between the two. Interesting!

    Issue 321 • Oct 6th 2017

  • Code

    Catching smiles with Google’s ML Kit on iOS

    I mentioned last week that MLKit was usable on iOS through Firebase and sure enough Martin Mitrevski has provided us with this example of smile detection with MLKit. 🤖

    Issue 352 • May 18th 2018

  • News

    The Future of Fabric

    This isn't surprising, I've been expecting an announcement ever since the acquisition last year. The bad news is that Firebase is now a required dependency if you want to continue using Crashlytics, and that some other features of Fabric are going away completely. It's not that Firebase is bad, far from it! You'll even get more features when you make the switch, but it is a big dependency if you were previously only using Crashlytics.

    Issue 369 • Sep 14th 2018

  • Code

    The Case for CloudKit

    Firebase seems to be taking over the world a bit, but before you commit to it for your next project read Andrew Bancroft's case for CloudKit. I still think if you're building something truly serious then rolling your own back end is probably the way to go, but I do like CloudKit too.

    Issue 364 • Aug 10th 2018

  • News

    Fabric is Joining Google

    I'm not sure how I feel about this, but I'm going to try not to judge it before Google get a chance to show what they do with it. Yes, there's a risk that some of these tools will be integrated so tightly with Firebase that they become less useful for those who don't use it, but equally maybe they won't. The Fabric tools never felt like a 100% natural fit at Twitter either, and would they survive the heavily rumoured acquisition by Disney? Who knows. Anyway, I think we have to wait and see what this means for the future of Fabric.

    Issue 284 • Jan 20th 2017

  • Comment

    So Google had their I/O conference this week and you almost certainly saw the demo of Google Duplex which has been everwhere since it happened. I don't want to get into it in too much detail here, but my thoughts can be summed up as follows:

    1. The assistant should probably identify itself at the start of the call by saying something like "This is the Google Assistant calling on behalf of ..." for a few reasons mentioned below.
    2. I don't have a problem with the ethics or concept of the technology for this specific use case. If the business receiving the call doesn't want this kind of call, they just implement a compatible online booking system and Google will use that instead of calling them. Of course we need to be very careful with how this kind of technology is used in the future, but I don't think this is the start of the apocalypse just yet.
    3. Yes, the tone of the assistant was a little direct/short but I wonder if this is to potentially limit the type of responses that the human will give? If I start a conversation being direct, the tone of the conversation is set by that and the assistant won't have to try and deal with the more complex responses of a less formal conversation. This would also happen if the assistant identified itself as mentioned in point 1.
    4. This is going to go wrong in the real world all the time and I'm really curious love to hear how it copes when that happens. At what point (if any) does it admit that it's a computer? Also, implementing point 1 would make this a lot easier.

    I'm quite sure Google thought about all of these points, at length, but these were my initial takes on it.

    Anyway, all of that has very little to do with iOS (or even mobile) development, so let's move on. As with WWDC, that main keynote is for the general public and it's the developer keynote that contains the real news for us, and there were several things that stood out to me:

    1. Google Assistant has a huge amount of support for third party apps, and so much more announced in this keynote. SiriKit started with a very limited set of possible integrations so that the supported domains are well understood. Google started with a much more open API and are now trying to use the data gathered to better understand the domains. Two very different approaches.
    2. There's a comedy naming situation going on with AR and ML frameworks but those technologies were definitely the theme for almost everything that Google talked about in the keynotes. MLKit is also available on iOS as it is part of Firebase which is interesting.
    3. App slices are really cool and I can see this becoming a much bigger part of how users interact with apps. It feels like iOS app extensions, but again with a different approach.
    4. Android Studio (and other Linux apps) can now run on Chrome OS. THIS IS THE YEAR OF LINUX ON THE DESKTOP! 😂

    Anyway all of that is interesting to look at but we're here to talk about iOS, so let's get on with those links.

    Issue 351 • May 11th 2018

Subscribe with

No spam, ever. We'll never share your email address and you can opt out at any time.

Subscribe with Safari to receive a push notification when new issues are published.

Visit this page in Safari on Mac OS X Mavericks or above to enable push notifications

©2011-2021 iOS Dev Weekly | Terms of Use | Privacy Policy | Sponsorship | Twitter | Suggest a Link

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Published with Curated