Alternatives to HockeyApp logo

Alternatives to HockeyApp

TestFlight, TestFairy, Fabric, Crashlytics, and fastlane are the most popular alternatives and competitors to HockeyApp.
168
158
+ 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. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

HockeyApp alternatives & related posts

TestFlight logo

TestFlight

1.1K
701
162
iOS beta testing on the fly.
1.1K
701
+ 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

    Utkarsh Mehta
    Senior Blockchain Developer · | 1 upvote · 4.8K views

    I created microservices with Kafka for message queue, Meteor for app development with JavaScript & TestFlight for iOS app development, Elasticsearch for logging SendGrid for automated mails. Git & GitHub for SCM.

    See more
    TestFairy logo

    TestFairy

    41
    76
    29
    Painless Beta Testing
    41
    76
    + 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
      In-App Feedback
    • 1
      Single Sign-On
    • 1
      App Distribution
    CONS OF TESTFAIRY
      Be the first to leave a con

      related TestFairy posts

      Fabric logo

      Fabric

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

        related Fabric posts

        Crashlytics logo

        Crashlytics

        1K
        615
        340
        The world's most powerful, yet lightest weight crash reporting solution. Free for everybody.
        1K
        615
        + 1
        340
        PROS OF CRASHLYTICS
        • 78
          Crash tracking
        • 56
          Mobile exception tracking
        • 53
          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
        • 3
          Android SDK
        • 2
          The UI is simple and it just works
        • 2
          Best UI
        • 2
          Light
        • 2
          Real-time
        • 2
          Seamless
        • 2
          Painless App Distribution
        • 2
          Crash Reporting
        • 2
          Beta distribution
        • 2
          Mobile Analytics
        • 2
          Deep Workflow Integration
        • 1
          IOS QA Deploy and tracking
        • 1
          Easy iOS Integration
        CONS OF CRASHLYTICS
          Be the first to leave a con

          related Crashlytics posts

          Алексей Нестерчук
          Shared insights
          on
          AWS ConfigAWS ConfigCrashlyticsCrashlytics

          From firebase Crashlytics, everything is simple, we install SDK and configs, and then we can see all the crashes. With AWS, it is not clear to me which service to use for the same purpose as configuring it. Correctly I understand that for automatic sending of all crashes, you need to use AWS Config?

          See more

          When we first built the ArifZefen app our focus was around validating our business assumptions and finding a good product fit. Once we got to a few thousand users, it became clear that we needed to make quality a priority and that meant we needed a reliable tool that will allow us to monitor the health of our app. Crashlytics (now Fabric by Twitter ) was on a short list of solutions we closely explored and we were very happy with its ease of integration and the consistency it brought to our Cocoa Touch (iOS) and Android SDK crash monitoring.

          Its daily pulse emails were also super informative in giving us a good sense of how each platform was doing in terms of crash-free and new users, daily actives and other relevant session data. These emails also surfaced any anomalies in daily trends, alerting us of any reason for concern. Overall, Crashlytics was instrumental in allowing us to quickly discover and diagnose crashes and it is one of the main reasons we were able to keep our app store ratings reasonable high. But perhaps even more importantly, we were able to set a high quality bar for our users that absent Crashlytics would have been difficult to maintain.

          See more
          fastlane logo

          fastlane

          641
          430
          74
          Connect all iOS deployment tools into one streamlined workflow
          641
          430
          + 1
          74
          PROS OF FASTLANE
          • 20
            Easy to use
          • 13
            Open Source
          • 13
            Itunes connect deployment
          • 11
            Incredible flexability
          • 9
            Third party integrations
          • 3
            Provisioning profile management
          • 3
            Certificate management
          • 1
            All in one iOS DevOps
          • 1
            Can be used for Android as well
          • 0
            Integrate anything with fastlane
          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

            Dear Community!

            I am researching for Mobile Application Management platform for managing android and ios release management in Fintech space. I see following options are good:

            Please suggest if you have better option.

            See more
            Firebase logo

            Firebase

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

            related Firebase posts

            Johnny Bell

            I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

            I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

            I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

            Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

            Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

            With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

            If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

            See more
            Collins Ogbuzuru
            Front-end dev at Evolve credit · | 15 upvotes · 7.3K views

            Your tech stack is solid for building a real-time messaging project.

            React and React Native are excellent choices for the frontend, especially if you want to have both web and mobile versions of your application share code.

            ExpressJS is an unopinionated framework that affords you the flexibility to use it's features at your term, which is a good start. However, I would recommend you explore Sails.js as well. Sails.js is built on top of Express.js and it provides additional features out of the box, especially the Websocket integration that your project requires.

            Don't forget to set up Graphql codegen, this would improve your dev experience (Add Typescript, if you can too).

            I don't know much about databases but you might want to consider using NO-SQL. I used Firebase real-time db and aws dynamo db on a few of my personal projects and I love they're easy to work with and offer more flexibility for a chat application.

            See more
            Jenkins logo

            Jenkins

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

            related Jenkins posts

            Tymoteusz Paul
            Devops guy at X20X Development LTD · | 23 upvotes · 8M 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
            JavaScript logo

            JavaScript

            349.6K
            266.2K
            8.1K
            Lightweight, interpreted, object-oriented language with first-class functions
            349.6K
            266.2K
            + 1
            8.1K
            PROS OF JAVASCRIPT
            • 1.7K
              Can be used on frontend/backend
            • 1.5K
              It's everywhere
            • 1.2K
              Lots of great frameworks
            • 896
              Fast
            • 745
              Light weight
            • 425
              Flexible
            • 392
              You can't get a device today that doesn't run js
            • 286
              Non-blocking i/o
            • 236
              Ubiquitousness
            • 191
              Expressive
            • 55
              Extended functionality to web pages
            • 49
              Relatively easy language
            • 46
              Executed on the client side
            • 30
              Relatively fast to the end user
            • 25
              Pure Javascript
            • 21
              Functional programming
            • 15
              Async
            • 13
              Full-stack
            • 12
              Setup is easy
            • 12
              Its everywhere
            • 11
              JavaScript is the New PHP
            • 11
              Because I love functions
            • 10
              Like it or not, JS is part of the web standard
            • 9
              Can be used in backend, frontend and DB
            • 9
              Expansive community
            • 9
              Future Language of The Web
            • 9
              Easy
            • 8
              No need to use PHP
            • 8
              For the good parts
            • 8
              Can be used both as frontend and backend as well
            • 8
              Everyone use it
            • 8
              Most Popular Language in the World
            • 8
              Easy to hire developers
            • 7
              Love-hate relationship
            • 7
              Powerful
            • 7
              Photoshop has 3 JS runtimes built in
            • 7
              Evolution of C
            • 7
              Popularized Class-Less Architecture & Lambdas
            • 7
              Agile, packages simple to use
            • 7
              Supports lambdas and closures
            • 6
              1.6K Can be used on frontend/backend
            • 6
              It's fun
            • 6
              Hard not to use
            • 6
              Nice
            • 6
              Client side JS uses the visitors CPU to save Server Res
            • 6
              Versitile
            • 6
              It let's me use Babel & Typescript
            • 6
              Easy to make something
            • 6
              Its fun and fast
            • 6
              Can be used on frontend/backend/Mobile/create PRO Ui
            • 5
              Function expressions are useful for callbacks
            • 5
              What to add
            • 5
              Client processing
            • 5
              Everywhere
            • 5
              Scope manipulation
            • 5
              Stockholm Syndrome
            • 5
              Promise relationship
            • 5
              Clojurescript
            • 4
              Because it is so simple and lightweight
            • 4
              Only Programming language on browser
            • 1
              Hard to learn
            • 1
              Test
            • 1
              Test2
            • 1
              Easy to understand
            • 1
              Not the best
            • 1
              Easy to learn
            • 1
              Subskill #4
            • 0
              Hard 彤
            CONS OF JAVASCRIPT
            • 22
              A constant moving target, too much churn
            • 20
              Horribly inconsistent
            • 15
              Javascript is the New PHP
            • 9
              No ability to monitor memory utilitization
            • 8
              Shows Zero output in case of ANY error
            • 7
              Thinks strange results are better than errors
            • 6
              Can be ugly
            • 3
              No GitHub
            • 2
              Slow

            related JavaScript posts

            Zach Holman

            Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

            But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

            But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

            Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

            See more
            Conor Myhrvold
            Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 9.6M views

            How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

            Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

            Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

            https://eng.uber.com/distributed-tracing/

            (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

            Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

            See more