Not any news on the Fabric dismantle. What brand stays alive? Will everything become Firebase?
There is a bit! Digits is moving to Firebase Auth, and Crashlytics will be the primary crash reporter for Firebase.
Open sourcing the Firebase SDKs
11–20 of 77 posts
Re: Open sourcing the Firebase SDKs
#12Not any news on the Fabric dismantle. What brand stays alive? Will everything become Firebase?
There is a bit! Digits is moving to Firebase Auth, and Crashlytics will be the primary crash reporter for Firebase.
What does it mean? Will I install crashlytics and my data will show up in Firebase console? Both consoles?
Re: Open sourcing the Firebase SDKs
#13Not any news on the Fabric dismantle. What brand stays alive? Will everything become Firebase?
There was a couple of pieces of news:
1. We're merging Digits into Firebase Authentiation
2. In the future, Crashlytics will be replacing Firebase Crash Reporting to become the default crash reporting tool in Firebase.
Hopefully this gives an idea of where we're going.
Re: Open sourcing the Firebase SDKs
#14Not any news on the Fabric dismantle. What brand stays alive? Will everything become Firebase?
There was a couple of pieces of news: 1. We're merging Digits into Firebase Authentiation 2. In the future, Crashlytics will be replacing Firebase Crash Reporting to become the default crash reporting tool in Firebase. Hopefully this gives an idea of where we're going.
Thanks! Are there any plans to move historic data from fabric to firebase or will I need to reconfigure and start clean?
Re: Open sourcing the Firebase SDKs
#15I didn't even know that the client was not open source. What makes this Firebase less risky than Parse or the recently deprecated Prediction API?
See the reply above by depoll: https://news.ycombinator.com/item?id=14362877
Re: Open sourcing the Firebase SDKs
#16Earlier quoted context omitted.
There is a bit! Digits is moving to Firebase Auth, and Crashlytics will be the primary crash reporter for Firebase.
What does it mean? Will I install crashlytics and my data will show up in Firebase console? Both consoles?
Fabric console right now - no changes, but that experience should get better over time.
Re: Open sourcing the Firebase SDKs
#17Earlier quoted context omitted.
There was a couple of pieces of news: 1. We're merging Digits into Firebase Authentiation 2. In the future, Crashlytics will be replacing Firebase Crash Reporting to become the default crash reporting tool in Firebase. Hopefully this gives an idea of where we're going.
Thanks! Are there any plans to move historic data from fabric to firebase or will I need to reconfigure and start clean?
Authentication data can be imported from Digits to Firebase. No changes to Crashlytics right now!
Re: Open sourcing the Firebase SDKs
#18[other Firebase founder] It was painful to read the article[1] this morning, especially since I was one of the people responsible for dropping the ball on getting Home Automation the credit to cover the overage a few weeks ago. We're working with the founder to make sure he's in a better spot. If you have similarly serious issues, my email is: james@firebase.com To address a couple of points that have been raised: 1.…
Until this[1] is fixed I'm not sure that Firebase would meet my needs for many projects. It's such a fundamental requirement to be able to query multiple fields without creating a mess of permutations of each field.
Re: Open sourcing the Firebase SDKs
#19I was an early Parse engineer (4th engineer to join the company) and now am the SDK engineering lead for Firebase. The experience of working on Firebase at Google is vastly different from Parse at Facebook, and it shows in Google’s continued commitment to building and expanding Firebase, integrating it with its Cloud Platform products, and otherwise pouring huge amounts of effort into making Firebase great for develo…
That's great! But it does make sense why google and FB would be taking different paths here. As much as I was disappointed with FB's decision on Parse, I can also understand the reasoning behind it and I actually think it was the right decisions for the company. In contrast, Google is playing in the cloud service vertical and investing in the future of Firebase is totally aligned with that objective.
Though it does seem kind of odd that facebook isn't playing in that space. I'd be curious to know their reasoning for not launching a competing product there.
Re: Open sourcing the Firebase SDKs
#20[other Firebase founder] It was painful to read the article[1] this morning, especially since I was one of the people responsible for dropping the ball on getting Home Automation the credit to cover the overage a few weeks ago. We're working with the founder to make sure he's in a better spot. If you have similarly serious issues, my email is: james@firebase.com To address a couple of points that have been raised: 1.…
To my discredit I enjoyed dumping on Google earlier today with the Firebase support issue article.
That being said this was a great response and I appreciate it. Also my first React Native app used Firebase and I have fond memories of setting that up :)
I like that item #1 was very direct...essentially: "look the support got worse and it's not good but we're working on it".
SIDE NOTE: I don't get how a lot of people today don't understand that using vague language in apologies doesn't help with apologies. It definitely used to, but then everyone started doing it, and now the cool / rare thing to do is to be direct. Maybe the pendulum will swing back someday. Until then thank you Mr.Google/Firebase/James person.