Crashlytics becoming the future crash reporter for Firebase

[Benjamin Drong]

With the recent announcement of Fabric's Crashlytics being acquired by Google and soon to become the main crash reporting tool for Firebase, I am wondering what the change will be like for developers currently using the Firebase Crash Reporting tools. 

Will we need to set up an account with Fabric and install their Crashlytics SDK in order to continue using Firebase crash reporting, or will the integration happen behind the scenes on the Firebase servers allowing us to continue using the Firebase SDK for crash reporting?

[Ian Barber]

Its still being worked on, but we're planning to make things as painless as we can whether you use crashlytics or firebase crash reporting. 

Right now, we're suggesting people new users go ahead and sign up with Fabric and integrate their SDK to use crashlytics, but we're hoping to make the process more integrated in the future! 

On Tue, May 23, 2017 at 10:36 AM, Benjamin Drong <b...@applicadia.us> wrote:

With the recent announcement of Fabric's Crashlytics being acquired by Google and soon to become the main crash reporting tool for Firebase, I am wondering what the change will be like for developers currently using the Firebase Crash Reporting tools. 

Will we need to set up an account with Fabric and install their Crashlytics SDK in order to continue using Firebase crash reporting, or will the integration happen behind the scenes on the Firebase servers allowing us to continue using the Firebase SDK for crash reporting?

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/b3ddbea6-b9ae-4e81-85a8-7375e46eb256%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chaz Estell]

Ian,

Quick question, why are you recommending people making new apps change now rather than wait for the integration to be complete? We would lose out on the event history feature, correct? Are there significant enough improvements to using Crashlytics now to be worth losing that feature, or is it a matter of that further updates will be easier if you work with Crashlytics currently?

--Chaz

On Tuesday, May 23, 2017 at 9:28:50 PM UTC-4, Ian Barber wrote:

Its still being worked on, but we're planning to make things as painless as we can whether you use crashlytics or firebase crash reporting. 

Right now, we're suggesting people new users go ahead and sign up with Fabric and integrate their SDK to use crashlytics, but we're hoping to make the process more integrated in the future! 

On Tue, May 23, 2017 at 10:36 AM, Benjamin Drong <b...@applicadia.us> wrote:

With the recent announcement of Fabric's Crashlytics being acquired by Google and soon to become the main crash reporting tool for Firebase, I am wondering what the change will be like for developers currently using the Firebase Crash Reporting tools. 

Will we need to set up an account with Fabric and install their Crashlytics SDK in order to continue using Firebase crash reporting, or will the integration happen behind the scenes on the Firebase servers allowing us to continue using the Firebase SDK for crash reporting?

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.

[Ian Barber]

We're mainly trying to signal forward intent - the feature sets are slightly different so I appreciate you may prefer to use Firebase Crash on a new app, but for those with no standing inclination we're recommending they go with crashlytics. 

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/a6f58997-cd03-481f-8231-00cdd53cf6b5%40googlegroups.com.