Timber is a logger with a small, extensible API which provides utility on top of Android's normal Log class. http://jakewharton.github.io/timber/
Pros :
Timber and Crashlytics can be used along with AppCrashHandler which elegently handles unhandled exceptions by restarting the app instead of showing the system dialogs displaying an error has occurred.
Read the article here link
@yanokwa @lognaturel @nribeka Any thoughts?
I'd be in favor of this. As a first pass, I think we should use Firebase Crash Reporting for production as proposed in #637 since it integrates well with Firebase Analytics. That should be an easy decision to revisit if needed since Trees can easily be swapped out.
(Also, this is merely speculation, but I wouldn't be surprised if Crashlytics was abandoned in favor of Firebase Analytics now that Google acquired Fabric.)
I'm in favour of using Fabric. I have used it before and it provides much better support and analysis as compared to firebase analytics
Yeah, that one will be gone. You know how google does stuff. Buy the company and absorb ("kill") the product 馃ぃ
@shobhitagarwal1612 You're going to have to say a little more to convince us!
Although I have a concern. We have seen earlier that GCM was merged with FCM and later the support for GCM is slowly being removed. Since Google now owns Fabric and already has Firebase Analytics. Will the fate of firebase analytics be the same? Are they going to be merged in the coming months? Any thoughts?
Found an article saying
Google acquires Twitter鈥檚 Fabric mobile app dev tools, will be integrated into Firebase
I think it's better to use Firebase instead of Fabric since all of the best features of both are going to be merged into Firebase eventually.
Closed in #821
Most helpful comment
Found an article saying
I think it's better to use Firebase instead of Fabric since all of the best features of both are going to be merged into Firebase eventually.