@brianegan

Thanks, @neiljaywarner -- it's a fair point! The reason I didn't use crashlytics: At the time, the Flutter team had only provided the Sentry plugin and no Crashlytics plugins existed.

It looks like there are now a couple of different plugins available on Pub that support crashlytics, but it's funny, I've continued to use sentry myself b/c it was working well for me and haven't evaluated them closely!

@sfshaza2 What are your thoughts on creating a recipe specifically for Crashlytics? If I do, how should I choose between the available plugins on pub -- I can definitely perform a general review of the code, maintenance, etc and make a subjective assessment. However, I wasn't sure if that was good enough in this case, since this could set an "accidental" standard that this is the Crashlytics plugin "The Flutter Team Endorses."

@Sfshaza Any more thoughts from you or the team on this one? I think I recently saw an official crashlytics plugin being developed, for example.

@brianegan : It looks like a Firebase Crashlytics package exists. Should we look to integrate this into the docs?

@atsansone Yah, totally makes sense now that there's a supported first-party / flutter favorite package. My previous comment was 4 years old before there was an official package.

Overall, the popularity difference between Crashlytics and Sentry doesn't look monumental (98% popularity compared to 100% popularity).

Therefore, perhaps keeping & renaming the current recipe and adding another recipe for Crashlytics might make sense?

@miquelbeltran, please review

Personally, I am not sure if a cookbook recipe is required here when the official docs from the product pages, e.g. https://firebase.google.com/docs/crashlytics/get-started?platform=flutter already cover this and are up to date.

I think we could replace the Sentry tutorial part with links to the official documentation, like we do in the Stage Management options list: https://docs.flutter.dev/data-and-backend/state-mgmt/options so we don't promote one over the other.

I agree with Miguels comment here. Given that the official docs are thorough, I would rather not add to our maintenance load. I also agree with the original comment: Sentry is far less popular than Crashlytics.

I recommend we either remove the Sentry recipe altogether and replace it with nothing, or we add a link to the both the Sentry and Crashlytics docs somewhere.

@sfshaza2 @atsansone WDYT?

I think it's fine to remove the Sentry recipe and not add one for Crashlytics, instead adding a general section titled something like "Track app crashes and errors" to https://docs.flutter.dev/testing/errors. It could also be a new page.

The section could talk a little background about why, and then link to the resources for various providers (Sentry, Crashlytics, Datadog, etc).

I think it's fine to remove the Sentry recipe and not add one for Crashlytics, instead adding a general section titled something like "Track app crashes and errors" to https://docs.flutter.dev/testing/errors. It could also be a new page.

The section could talk a little background about why, and then link to the resources for various providers (Sentry, Crashlytics, Datadog, etc).

This sounds like a good plan to me.

I also did my due diligence, and they Sentry cookbook is among the ~10 lowest performing pages, measured by pageviews.

@parlough : I'll leave it to you to refactor changes in this space. Thanks!

I'm not going to have time to work on this any time soon, so I'm unassigning myself. Happy to help anyone that wants to tackle this though, thanks!