Alternatives to HockeyApp logo

Alternatives to HockeyApp

TestFlight, TestFairy, Fabric, Crashlytics, and fastlane are the most popular alternatives and competitors to HockeyApp.
168
140
+ 1
38

What is HockeyApp and what are its top alternatives?

HockeyApp is the best way to collect live crash reports, get feedback from your users, distribute your betas, and analyze your test coverage.
HockeyApp is a tool in the Beta Testing / Mobile App Distribution category of a tech stack.

Top Alternatives to HockeyApp

  • TestFlight

    TestFlight

    With TestFlight, developers simply upload a build, and the testers can install it directly from their device, over the air. ...

  • TestFairy

    TestFairy

    When testing apps in the crowd, you never know what exactly was done, and what went wrong on the client side. TestFairy shows you a video of the exact test that was done, including CPU, memory, GPS, network and a lot more. ...

  • Fabric

    Fabric

    Fabric is a Python (2.5-2.7) library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks. It provides a basic suite of operations for executing local or remote shell commands (normally or via sudo) and uploading/downloading files, as well as auxiliary functionality such as prompting the running user for input, or aborting execution. ...

  • Crashlytics

    Crashlytics

    Instead of just showing you the stack trace, Crashlytics performs deep analysis of each and every thread. We de-prioritize lines that don't matter while highlighting the interesting ones. This makes reading stack traces easier, faster, and far more useful! Crashlytics' intelligent grouping can take 50,000 crashes, distill them down to 20 unique issues, and then tell you which 3 are the most important to fix. ...

  • fastlane

    fastlane

    fastlane lets you define and run your deployment pipelines for different environments. It helps you unify your app’s release process and automate the whole process. fastlane connects all fastlane tools and third party tools, like CocoaPods. ...

  • Firebase

    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • Jenkins

    Jenkins

    In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project. ...

  • Fabric by Twitter

    Fabric by Twitter

    Installing and managing a wide range of SDKs can be cumbersome and complex. Fabric solves this problem by combining all seven of our SDKs under one roof and organizing them into three Kits: the Crashlytics Kit, the Twitter Kit, and the MoPub Kit. ...

HockeyApp alternatives & related posts

TestFlight logo

TestFlight

1.1K
665
162
iOS beta testing on the fly.
1.1K
665
+ 1
162
PROS OF TESTFLIGHT
  • 62
    Must have for ios development
  • 49
    Beta testing
  • 19
    Easy setup
  • 10
    Easy way to push out updates for internal testers
  • 7
    In-App Updates
  • 5
    Crash Logging
  • 4
    Checkpoints
  • 3
    Multiple platforms
  • 2
    Remote Logging
  • 1
    Sessions
CONS OF TESTFLIGHT
    Be the first to leave a con

    related TestFlight posts

    TestFairy logo

    TestFairy

    41
    70
    29
    Painless Beta Testing
    41
    70
    + 1
    29
    PROS OF TESTFAIRY
    • 8
      Get video rec of the user on your app
    • 4
      Landing Page
    • 4
      Better design
    • 3
      JIRA Integration
    • 2
      Cross-platform
    • 2
      Supports Enterprise IPA's (TestFlight doesn't/didn't)
    • 2
      GitHub Integration
    • 1
      Application full Log information
    • 1
      Single Sign-On
    • 1
      App Distribution
    • 1
      In-App Feedback
    CONS OF TESTFAIRY
      Be the first to leave a con

      related TestFairy posts

      Fabric logo

      Fabric

      415
      278
      74
      Simple, Pythonic remote execution and deployment
      415
      278
      + 1
      74
      PROS OF FABRIC
      • 22
        Python
      • 21
        Simple
      • 5
        Low learning curve, from bash script to Python power
      • 5
        Installation feedback for Twitter App Cards
      • 3
        Easy to add any type of job
      • 3
        Single config file
      • 3
        Easy on maintainance
      • 3
        Installation? pip install fabric... Boom
      • 3
        Agentless
      • 2
        Easily automate any set system automation
      • 1
        Backward compatibility
      • 1
        Remote sudo execution
      • 1
        Crash Analytics
      • 1
        Flexible
      CONS OF FABRIC
        Be the first to leave a con

        related Fabric posts

        Crashlytics logo

        Crashlytics

        960
        554
        337
        The world's most powerful, yet lightest weight crash reporting solution. Free for everybody.
        960
        554
        + 1
        337
        PROS OF CRASHLYTICS
        • 77
          Crash tracking
        • 56
          Mobile exception tracking
        • 52
          Free
        • 37
          Easy deployment
        • 25
          Ios
        • 15
          Great ui
        • 11
          Great reports
        • 10
          Android
        • 8
          Advanced Logging
        • 7
          Monitor Tester Lifecycle
        • 3
          Mac APP and IDE Plugins
        • 3
          Great User Experience
        • 3
          In Real-Time
        • 3
          iOS SDK
        • 3
          Security
        • 2
          Real-time
        • 2
          Crash Reporting
        • 2
          Beta distribution
        • 2
          Mobile Analytics
        • 2
          Best UI
        • 2
          Deep Workflow Integration
        • 2
          Android SDK
        • 2
          The UI is simple and it just works
        • 2
          Light
        • 2
          Seamless
        • 2
          Painless App Distribution
        • 1
          Easy iOS Integration
        • 1
          IOS QA Deploy and tracking
        CONS OF CRASHLYTICS
          Be the first to leave a con

          related Crashlytics posts

          fastlane logo

          fastlane

          475
          349
          71
          Connect all iOS deployment tools into one streamlined workflow
          475
          349
          + 1
          71
          PROS OF FASTLANE
          • 19
            Easy to use
          • 13
            Open Source
          • 13
            Itunes connect deployment
          • 11
            Incredible flexability
          • 8
            Third party integrations
          • 3
            Certificate management
          • 3
            Provisioning profile management
          • 1
            All in one iOS DevOps
          • 0
            Integrate anything with fastlane
          • 0
            Can be used for Android as well
          CONS OF FASTLANE
            Be the first to leave a con

            related fastlane posts

            Hi, I am doing automation for mobile app (iOS & Android). Currently, I am using Apache Maven build tool. Can someone tell me which out of these 3 tools is the best? (fastlane, Gradle, Maven). Apart from that, we are using CircleCI.

            See more

            Firebase Cloud Firestore Cloud Functions for Firebase Google App Engine React React Native React Native Firebase NativeBase Twilio Dwolla.js Yarn fastlane Bitbucket Slack LastPass

            See more
            Firebase logo

            Firebase

            28.3K
            24K
            1.9K
            The Realtime App Platform
            28.3K
            24K
            + 1
            1.9K
            PROS OF FIREBASE
            • 362
              Realtime backend made easy
            • 265
              Fast and responsive
            • 235
              Easy setup
            • 209
              Real-time
            • 187
              JSON
            • 130
              Free
            • 122
              Backed by google
            • 82
              Angular adaptor
            • 65
              Reliable
            • 36
              Great customer support
            • 27
              Great documentation
            • 23
              Real-time synchronization
            • 21
              Mobile friendly
            • 18
              Rapid prototyping
            • 13
              Great security
            • 12
              Automatic scaling
            • 11
              Freakingly awesome
            • 8
              Angularfire is an amazing addition!
            • 8
              Super fast development
            • 8
              Chat
            • 6
              Ios adaptor
            • 6
              Awesome next-gen backend
            • 5
              Built in user auth/oauth
            • 5
              Firebase hosting
            • 4
              Speed of light
            • 4
              Very easy to use
            • 3
              Great
            • 3
              Brilliant for startups
            • 3
              It's made development super fast
            • 2
              JS Offline and Sync suport
            • 2
              I can quickly create static web apps with no backend
            • 2
              Great all-round functionality
            • 2
              The concurrent updates create a great experience
            • 2
              Low battery consumption
            • 1
              Easy Reactjs integration
            • 1
              Push notification
            • 1
              Cloud functions
            • 1
              Easy to use
            • 1
              Faster workflow
            • 1
              Large
            • 1
              Serverless
            • 1
              .net
            • 1
              Good Free Limits
            • 1
              Free SSL
            • 1
              Free hosting
            • 1
              Free authentication solution
            • 1
              CDN & cache out of the box
            CONS OF FIREBASE
            • 29
              Can become expensive
            • 15
              No open source, you depend on external company
            • 15
              Scalability is not infinite
            • 9
              Not Flexible Enough
            • 5
              Cant filter queries
            • 3
              Very unstable server
            • 2
              Too many errors
            • 2
              No Relational Data
            • 1
              No offline sync

            related Firebase posts

            Stephen Gheysens
            Senior Solutions Engineer at Twilio · | 14 upvotes · 369.3K views

            Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

            My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

            See more
            Tassanai Singprom

            This is my stack in Application & Data

            JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

            My Utilities Tools

            Google Analytics Postman Elasticsearch

            My Devops Tools

            Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

            My Business Tools

            Slack

            See more
            Jenkins logo

            Jenkins

            43.4K
            35.9K
            2.2K
            An extendable open source continuous integration server
            43.4K
            35.9K
            + 1
            2.2K
            PROS OF JENKINS
            • 521
              Hosted internally
            • 465
              Free open source
            • 314
              Great to build, deploy or launch anything async
            • 243
              Tons of integrations
            • 210
              Rich set of plugins with good documentation
            • 109
              Has support for build pipelines
            • 72
              Open source and tons of integrations
            • 63
              Easy setup
            • 61
              It is open-source
            • 54
              Workflow plugin
            • 11
              Configuration as code
            • 10
              Very powerful tool
            • 9
              Many Plugins
            • 8
              Continuous Integration
            • 8
              Great flexibility
            • 8
              Git and Maven integration is better
            • 6
              Github integration
            • 6
              100% free and open source
            • 6
              Slack Integration (plugin)
            • 5
              Easy customisation
            • 5
              Self-hosted GitLab Integration (plugin)
            • 4
              Docker support
            • 3
              Excellent docker integration
            • 3
              Platform idnependency
            • 3
              Fast builds
            • 3
              Pipeline API
            • 2
              Customizable
            • 2
              Can be run as a Docker container
            • 2
              It`w worked
            • 2
              JOBDSL
            • 2
              Hosted Externally
            • 2
              It's Everywhere
            • 2
              AWS Integration
            • 1
              NodeJS Support
            • 1
              PHP Support
            • 1
              Ruby/Rails Support
            • 1
              Universal controller
            • 1
              Easily extendable with seamless integration
            • 1
              Build PR Branch Only
            CONS OF JENKINS
            • 12
              Workarounds needed for basic requirements
            • 8
              Groovy with cumbersome syntax
            • 6
              Limited abilities with declarative pipelines
            • 6
              Plugins compatibility issues
            • 5
              Lack of support
            • 4
              No YAML syntax
            • 2
              Too tied to plugins versions

            related Jenkins posts

            Tymoteusz Paul
            Devops guy at X20X Development LTD · | 23 upvotes · 4.7M views

            Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

            It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

            I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

            We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

            If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

            The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

            Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

            See more
            Thierry Schellenbach

            Releasing new versions of our services is done by Travis CI. Travis first runs our test suite. Once it passes, it publishes a new release binary to GitHub.

            Common tasks such as installing dependencies for the Go project, or building a binary are automated using plain old Makefiles. (We know, crazy old school, right?) Our binaries are compressed using UPX.

            Travis has come a long way over the past years. I used to prefer Jenkins in some cases since it was easier to debug broken builds. With the addition of the aptly named “debug build” button, Travis is now the clear winner. It’s easy to use and free for open source, with no need to maintain anything.

            #ContinuousIntegration #CodeCollaborationVersionControl

            See more
            Fabric by Twitter logo

            Fabric by Twitter

            169
            76
            2
            Mobile developer platform.
            169
            76
            + 1
            2
            PROS OF FABRIC BY TWITTER
            • 1
              Real-time analytics
            • 1
              Easy BETA distribution + monitoring
            CONS OF FABRIC BY TWITTER
              Be the first to leave a con

              related Fabric by Twitter posts