TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Firebase Crashlytics

    Score9.8 out of 10
    N/ACrashlytics 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

    Git

    Score10 out of 10
    N/AN/AN/A
    Pricing
    Firebase CrashlyticsGit
    Editions & Modules
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    Firebase CrashlyticsGit
    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
    Firebase CrashlyticsGit
    Considered Both Products
    Google
    No answer on this topic
    Open Source
    No answer on this topic
    Key User Insights
    Would buy again
    No answers on this topic
    100%
    Would buy again
    12 Answers
    Delivers good value for the price
    No answers on this topic
    100%
    Delivers good value for the price
    11 Answers
    Happy with the feature set
    No answers on this topic
    100%
    Happy with the feature set
    12 Answers
    Lived up to sales and marketing promises
    No answers on this topic
    100%
    Lived up to sales and marketing promises
    9 Answers
    Implementation went as expected
    No answers on this topic
    100%
    Implementation went as expected
    9 Answers
    Best Alternatives
    Firebase CrashlyticsGit
    Small Businesses
    Branch
    Score6.3 out of 10
    GitHub
    Score9.2 out of 10
    Medium-sized Companies
    AppsFlyer
    Score5.5 out of 10
    GitHub
    Score9.2 out of 10
    Enterprises
    Flurry Analytics (discontinued)
    Score9 out of 10
    Perforce P4
    Score7.5 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    Firebase CrashlyticsGit
    Likelihood to Recommend
    10.0
    (8 ratings)
    10.0
    (36 ratings)
    Likelihood to Renew
    10.0
    (1 ratings)
    10.0
    (1 ratings)
    Usability
    10.0
    (1 ratings)
    9.0
    (1 ratings)
    Support Rating
    -
    (0 ratings)
    8.5
    (11 ratings)
    Implementation Rating
    -
    (0 ratings)
    9.0
    (1 ratings)
    User Testimonials
    Firebase CrashlyticsGit
    Likelihood to Recommend
    Google
    Firebase Crashlytics is a no-brainer if you are already using any of the other Firebase suite of products, as its integration is very easy if you are already using these in your app. If you have cross-platform Android, iOS, and macOS apps, you should also consider Firebase Crashlytics to provide a unified across your platforms. If your app is only on Android or only on Apple, then you may be better off remaining with the default Apple Developer or Google Play Developer Console crash collection experiences.
    Incentivized
    Read full review
    Open Source
    GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
    Incentivized
    Read full review
    Pros
    Google
    • Providing stack traces that are useful when users have crashes.
    • Tracking crashes per version (app and OS) so we know whether to release a version to everyone instead of a subset.
    • Provides trending crsahes/problems if there's a spike in issues so we can get on it quickly.
    Incentivized
    Read full review
    Open Source
    • Ability to create branches off current releases to modify code that can be tested in a separate environment.
    • Each developer had their own local copy of branches so it minimizes mistakes being made.
    • Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
    • Conflicts are displayed nicely so that developers can resolve with ease.
    Incentivized
    Read full review
    Cons
    Google
    • Navigation between the issue listing and details is something difficult to understand for the new user.
    • Pannel takes time in loading may be because of analytics data but it can be reduce.
    • Not provide accurate line number in case of proguarded apps.
    Read full review
    Open Source
    • There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master.
    • Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this.
    • Many different GUIs, many people (including myself) opt to just use the command-line.
    Incentivized
    Read full review
    Likelihood to Renew
    Google
    Because its fulfilling our basic and necessary requirements that can be an only and enough reason to renew the subscription.
    Read full review
    Open Source
    Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
    Incentivized
    Read full review
    Usability
    Google
    It is very easy for non-developer staff to use the Firebase Console and gather information for the development team. Developers will find it straightforward to integrate Firebase Crashlytics into new or existing codebases using Google's in-depth developer documentation. I cannot think of an easier cross-platform solution to use, and because of that I wish it supported more platforms!
    Incentivized
    Read full review
    Open Source
    Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.
    Incentivized
    Read full review
    Support Rating
    Google
    No answers on this topic
    Open Source
    I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
    Incentivized
    Read full review
    Implementation Rating
    Google
    No answers on this topic
    Open Source
    It's easy to set up and get going.
    Incentivized
    Read full review
    Alternatives Considered
    Google
    Truly speaking, it is also a quite good tool for crash reports, but Firebase Crashlytics was better to use when you are using the Firebase Realtime database as your DB, so the integrations become much easier.
    Incentivized
    Read full review
    Open Source
    I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different.
    The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy.
    It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
    Incentivized
    Read full review
    Return on Investment
    Google
    • Fix bugs within hours rather than days or weeks
    • Retain users longer by reducing their frustration due to crashes
    • Keep management happy that our app is stable & bug-free
    Incentivized
    Read full review
    Open Source
    • Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
    • Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
    • Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
    Incentivized
    Read full review
    ScreenShots