Bugzilla vs. Firebase Crashlytics

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Bugzilla
Score 7.7 out of 10
N/A
N/AN/A
Firebase Crashlytics
Score 8.1 out of 10
N/A
Crashlytics is a mobile analytics tool which helps users find the exact line of code that their app crashed on, providing granular insight into mobile app performance and user experience. Crashlytics was acquired by Google in 2017 and is now offered as part of the Firebase product.N/A
Pricing
BugzillaFirebase Crashlytics
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
BugzillaFirebase Crashlytics
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
BugzillaFirebase Crashlytics
Top Pros
Top Cons
Best Alternatives
BugzillaFirebase Crashlytics
Small Businesses
GitLab
GitLab
Score 8.9 out of 10
Smartlook
Smartlook
Score 8.5 out of 10
Medium-sized Companies
GitLab
GitLab
Score 8.9 out of 10
Flurry Analytics
Flurry Analytics
Score 9.0 out of 10
Enterprises
GitLab
GitLab
Score 8.9 out of 10
Flurry Analytics
Flurry Analytics
Score 9.0 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
BugzillaFirebase Crashlytics
Likelihood to Recommend
7.7
(18 ratings)
8.6
(7 ratings)
Likelihood to Renew
6.0
(10 ratings)
10.0
(1 ratings)
Usability
9.0
(3 ratings)
-
(0 ratings)
Availability
9.0
(3 ratings)
-
(0 ratings)
Performance
8.0
(2 ratings)
-
(0 ratings)
Support Rating
5.1
(3 ratings)
-
(0 ratings)
In-Person Training
9.0
(1 ratings)
-
(0 ratings)
Implementation Rating
8.0
(2 ratings)
-
(0 ratings)
Configurability
9.0
(1 ratings)
-
(0 ratings)
Ease of integration
9.0
(1 ratings)
-
(0 ratings)
Product Scalability
9.0
(1 ratings)
-
(0 ratings)
Vendor post-sale
7.0
(1 ratings)
-
(0 ratings)
Vendor pre-sale
8.0
(1 ratings)
-
(0 ratings)
User Testimonials
BugzillaFirebase Crashlytics
Likelihood to Recommend
Open Source
Buzilla is easy to use and provides basic functionality to use as a bug tracking tool. If big size attachments are allowed it would have been great. Also with Bugzilla home->Test management area is improved by allowing multiple sections it would be awesome!
Read full review
Google
Crashlytics is almost a defacto standard in the Android world for tracking crashes in the field. I've used it on the last 4 Android projects I've been on. It's not as helpful on iOS' stacktraces but I'm not sure if anything would be better because iOS stack traces are from ObjC code which is not as useful as Java stacktraces.
Read full review
Pros
Open Source
  • Open source! No license fee involved, no limit to the number of licenses.
  • Easy to install and maintain. Installation is very easy and hardly needs any maintenance efforts, except when migrating from one version to other. Each project can have its own group of users.
  • Includes all the core features/fields that are needed to log a software bug/issue.
  • Multiple attachments are possible, supports various formats.
  • Good for reporting. Filtering mechanism lets you query bugs by various parameters.
Read full review
Google
  • Can get the device detail an actual state like RAM, Storage, Display Size, etc.
  • Can get the class name and line number where crash occur.
  • Its work in realtime so we can reduce the time of issue finding and resolution.
Read full review
Cons
Open Source
  • Cloud Based. I'd like to see bugzilla be cloud based. The company I currently work with made a final decision to change db's for this specific reason. Due to the frequency of travel in this company, they need access to bugzilla from differing national / international locations.
  • Larger File Attachments. I believe the limit of a bugzilla content upload is 4 megabytes. For many of our video'd issues, this file size is simply impractical without the additional effort exertion on video compressor applications.
Read full review
Google
  • Sometimes UI of Firebase Crashlytics is quit difficult to understand for new users.
  • There can be a proper discretion for all the features that is offered.
  • There can be api crash report also.
Read full review
Likelihood to Renew
Open Source
For future projects I will look at something that is hosted in the cloud that I don't have to manage. I would also like something that has a more modern feel to allow my customers to use it as well as my employees.
Read full review
Google
Because its fulfilling our basic and necessary requirements that can be an only and enough reason to renew the subscription.
Read full review
Usability
Open Source
This is a pretty straightforward system. You put in the bug details, a ticket is created, the team is notified. The user interface reflects this very simple and straightforward flow. It's certainly much easier than trying to track bugs with using Excel and email.
Read full review
Google
No answers on this topic
Reliability and Availability
Open Source
I used it.
Read full review
Google
No answers on this topic
Performance
Open Source
I like this rating.
Read full review
Google
No answers on this topic
Support Rating
Open Source
Since it is open source, it doesn't have customer service. However, the amount of information on forums is vast. If you can wade through it, you'll get what you need
Read full review
Google
No answers on this topic
In-Person Training
Open Source
I know it.
Read full review
Google
No answers on this topic
Implementation Rating
Open Source
Implementation was pretty simple. Particularly because the product cannot be customized so there is not much to do apart from getting it up and running.
Read full review
Google
No answers on this topic
Alternatives Considered
Open Source
We migrated away from the whole suite of Rational tools because of their massive complexity around administration and inflexibility regarding workflows. In addition, the suite was insanely expensive, and users hated the usability of the tools. We evaluated, and liked JIRA, but because the organization was looking for cost savings, we ended up going with Bugzilla and it's FOSS model so as to avoid ongoing costs.
Read full review
Google
As mentioned previously, the only realistic competitor to Crashlytics is Instabug (backed by Y Combinator in the W16 class). While Crashlytics is focused on actual crashes, Instabug's main innovation is in collecting feedback from users for non-crash bugs. While non-crash bugs are a substantial category of bugs, Instabug's pricing is quite steep. As soon as you go beyond the most basic features your monthly bill spikes to $124 - $499 per month, whereas Crashlytics is 100% free (for all usage levels and all enterprise features). Based on this, I've never tried Instabug because the ROI just wasn't there.
Read full review
Scalability
Open Source
I used it
Read full review
Google
No answers on this topic
Return on Investment
Open Source
  • It has made the SDLC process more efficient. Bugs were logged and tracked in emails or in Excel sheets leading to slow communication and at time version issues with multiple files. Being an online tool, Bugzilla solved those issues, improved communication, instant status updates and improved efficiency.
  • We have used Bugzilla with a lot of federal goverment agencies (DHS, CMS, SAMHSA, CDC, HHS etc). Project Directors adn Principle Investigators were at times given access to Bugzilla which provided a snapshot of open vs closed issues.
  • Some groups would resist using Bugzilla with the email reminders being the main reason. Turning off or reminding them of features where we can 'control' email notification helped a lot.
Read full review
Google
  • Allows us to easily share crash data with clients.
  • Provides confidence to our developers and project teams by having trust in the data that is being reported.
  • Allows us to quickly and efficiently address fatal crashes.
Read full review
ScreenShots