Need advice about which tool to choose?Ask the StackShare community!
HockeyApp vs TeamCity: What are the differences?
Developers describe HockeyApp as "Manage your betas and collect live crash reports for iOS, Android, Windows Phone, and OS X apps". HockeyApp is the best way to collect live crash reports, get feedback from your users, distribute your betas, and analyze your test coverage. On the other hand, TeamCity is detailed as "TeamCity is an ultimate Continuous Integration tool for professionals". TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
HockeyApp belongs to "Beta Testing / Mobile App Distribution" category of the tech stack, while TeamCity can be primarily classified under "Continuous Integration".
Some of the features offered by HockeyApp are:
- Crash Reports- HockeyApp offers the most reliable and complete crash reporting for beta and App Store versions using open source frameworks. Providing full server-side symbolication with class names, methods, line numbers, and automatic grouping of similar crash reports.
- Feedback- HockeyApp allows you to communicate with your customers. Users can create a support request, post an idea, or discuss a problem right from within the app.
- Distribution- Upload your beta versions to HockeyApp and distribute them to your beta testers. Integrate our open-source SDK and your app will automatically be able to detect updates and offer the updates right within the app.Analytics- By integrating our SDK into your app, you'll get advanced metrics to get a better overview of the testing for your app. See which devices were tested, which testers used the app for how long, and which language was tested.
On the other hand, TeamCity provides the following key features:
- Automate code analyzing, compiling, and testing processes, with having instant feedback on build progress, problems, and test failures, all in a simple, intuitive web-interface
- Simplified setup: create projects from just a VCS repository URL
- Run multiple builds and tests under different configurations and platforms simultaneously
"Crash analytics" is the primary reason why developers consider HockeyApp over the competitors, whereas "Easy to configure" was stated as the key factor in picking TeamCity.
Stack Exchange, Yammer, and AX Semantics are some of the popular companies that use TeamCity, whereas HockeyApp is used by Harvest, SOLEDOS GmbH, and Brigade. TeamCity has a broader approval, being mentioned in 168 company stacks & 51 developers stacks; compared to HockeyApp, which is listed in 50 company stacks and 10 developer stacks.
Pros of HockeyApp
- Crash analytics17
- Cross-platform11
- Mobile application distribution5
- JIRA Integration2
- Open source2
- GitHub Integration1
Pros of TeamCity
- Easy to configure61
- Reliable and high-quality37
- User friendly32
- On premise32
- Github integration32
- Great UI18
- Smart16
- Free for open source12
- Can run jobs in parallel12
- Crossplatform8
- Chain dependencies5
- Fully-functional out of the box5
- Great support by jetbrains4
- REST API4
- Projects hierarchy4
- 100+ plugins4
- Personal notifications3
- Free for small teams3
- Build templates3
- Per-project permissions3
- Upload build artifacts2
- Smart build failure analysis and tracking2
- Ide plugins2
- GitLab integration2
- Artifact dependencies2
- Official reliable support2
- Build progress messages promoting from running process2
- Repository-stored, full settings dsl with ide support1
- Built-in artifacts repository1
- Powerful build chains / pipelines1
- TeamCity Professional is FREE1
- High-Availability0
- Hosted internally0
Sign up to add or upvote prosMake informed product decisions
Cons of HockeyApp
Cons of TeamCity
- High costs for more than three build agents3
- Proprietary2
- User-friendly2
- User friendly2