Skip to main content
TrustRadius
Applause

Applause

Overview

What is Applause?

Applause headquartered in Framingham in Massachusetts offers application testing services.

Read more
Recent Reviews

TrustRadius Insights

Applause is a versatile platform that is used by companies for functional in-the-wild testing and localization testing. Test leads can …
Continue reading

Applauding Applause

8 out of 10
September 22, 2015
We used Applause to help with our functional testing on a variety of web applications we were developing and updating. We had a large …
Continue reading

Great Service.

8 out of 10
September 21, 2015
Incentivized
I like that Applause can help me test my apps using multiple devices and increase the quality of my apps; usually it saves me a lot of …
Continue reading

Applause for Applause

10 out of 10
September 21, 2015
Applause provides an efficient model of testing that will allow a startup access to thousands of professional testers. A company can …
Continue reading
Read all reviews
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Applause?

Applause headquartered in Framingham in Massachusetts offers application testing services.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

10 people also want pricing

Alternatives Pricing

What is Centercode?

Centercode Connect is a hosted software platform that provides all of the tools needed to run a beta program: recruiting, NDA management, product distribution, surveys, bug reports, forums, reporting, and more.

What is AutomationHQ?

AutomationHQ™ (AHQ) is a complete TAAS (Test Automation As Service) solution. Its NLP driven, cloud-based No-Code test automation platform is presented as ideal for agile delivery team. Any one in agile team can develop In-Sprint test automation in plain English with AHQ. User can create virtual…

Return to navigation

Product Details

What is Applause?

Applause Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(16)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Applause is a versatile platform that is used by companies for functional in-the-wild testing and localization testing. Test leads can handle everything within the Applause platform, from managing testers to bug triage, making it a comprehensive solution. One of the key use cases of Applause is its ability to facilitate testing on multiple mobile apps. With the challenge of testing on various platforms, devices, and OS permutations, Applause provides a solution by offering access to a large resource of global testers who can simulate real-world scenarios. This allows companies to ensure their apps are robust and ready for launch. Additionally, Applause is utilized by engineering and product teams for testing new products and new versions of existing products. It serves as a supplement to internal QA teams by providing access to thousands of professional testers, reducing the overall cost of development while ensuring high-quality applications.

Another significant use case of Applause is its Mobile Beta Management tools, which aid in pre-launch app development and user feedback. By integrating these tools into the development process, companies can gather valuable insights from beta users and make necessary improvements before launching their apps to the market. Additionally, Applause is also used for functional testing and high-level review of web applications, complementing internal testing efforts. It helps companies identify bugs in both mobile and web portal apps, allowing them to create comprehensive test plans to ensure app quality.

Furthermore, Information Technology departments rely on Applause to ensure the usability of mobile applications. With its capabilities to test apps on multiple devices, Applause reduces both the time and cost associated with manual testing. Lastly, small companies benefit from Applause as it helps them ramp up QA resources in a cost-efficient manner. By leveraging established QA experts available through the platform, these companies can ensure that their apps are thoroughly tested without having to invest heavily in building an internal QA team.

Overall, Applause offers a range of use cases that cater to different needs across industries. Its comprehensive testing capabilities, access to a global network of testers, and cost-efficiency make it a valuable tool for companies looking to enhance the quality of their mobile and web applications.

Wide range of devices and OS versions covered: Many users have found that the in-the-wild testing provided by Applause is essential as it allows for a wide range of devices and operating system versions to be covered. This type of testing provides better coverage of the product, as different minds approach workflows differently.

Helpful test lead support: Users appreciate the care provided by the test lead at Applause, as they are helpful in bug triage and transferring bugs to internal systems. This support saves time and improves efficiency.

Excellent platform, device, and OS coverage: The excellent platform, device, and operating system coverage provided by Applause eliminate the need for purchasing a large number of devices for in-house testing. This not only saves money but also provides a better return on investment.

Expensive Pricing: Some users have mentioned that the service is quite expensive, indicating that it may not provide a good value for the price.

Time-Consuming First Year: Several reviewers have expressed that the first year of using the service can be time-consuming and challenging to find the right balance between utilizing all features and managing other tasks. This aspect may require additional effort from users as they navigate through this initial period, potentially affecting their overall efficiency.

Shallow Testing Focus: According to customer feedback, testers may not go deep enough during testing as they are paid based on bugs found rather than ensuring comprehensive coverage. This results in a focus on low-hanging fruit and potential gaps in identifying more complex issues or edge cases within the system.

Users have made the following recommendations based on their experience with Applause:

  • Plan testing in detail before using Applause. Thorough planning helps ensure comprehensive coverage of the application and efficient testing.

  • Trial the service and develop a strategy before fully implementing Applause. This allows organizations to assess its suitability and determine how to integrate it effectively.

  • Treat Applause as an extension of the in-house test team. Working closely with project managers and test team leaders enhances collaboration and maximizes the benefits of using Applause.

These recommendations emphasize the importance of detailed planning, strategic implementation, and strong collaboration when utilizing Applause for application testing purposes.

Attribute Ratings

Reviews

(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
Martin Å tefan | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
We use Applause in the quality engineering department for functional in-the-wild testing and localization testing. We started utilizing the service back in 2011 and the relationship evolved during time. Currently we have couple of test leads handling everything within the Applause platform, the testers and bug triage that come from the crowd source testing. The test leads also transfer valid tickets to our internal bug tracking system, which makes the collaboration between our companies seamless. Applause is utilized for multiple, mostly mobile, apps testing.
  • In-the-wild testing - it cannot be done internally. It's impossible to cover the wide matrix of devices and OS versions.
  • Exploratory testing - more eyes see more. Every mind is unique and thinks of a workflow differently - provides better coverage of the product.
  • Care provided by test lead is essential - they help a lot with initial bug triage and bug transfer to our internal systems.
  • Retest of found tickets once they are fixed - saves time!
  • Applause people make a good effort to create a relationship, it's not just business.
  • The service is quite expensive.
  • The first year of using the service is about finding the right balance. It can initially be more time consuming then the previous model without Applause service.
  • The model motivates the testers to not go very deep during testing - they are paid by bugs found. Means there are cases when they go for only the low hanging fruit.
The key value of Applause lays in exploratory testing and in-the-wild testing. Besides these, it's impossible to cover all combinations of devices and OS versions internally. That's where Applause comes in really handy! Also localization testing is really easy since native speakers can be brought in. However - for more complex applications, training is necessary and building the test community as well.
  • Saves time spent on regression - internal resources can focus on more important tasks.
  • Saves money on device / OS coverage.
  • Price for a bug fixed is lower than price for a bug hot fixed.
By the time we signed the contract, there was no competition to Applause (back in time the company was called uTest). Ever since, we didn't evaluate anyone else because we built a very close relationship, which works for both sides. I think Applause is the furthest in building the test community.
20
Internally Applause is utilized by individual contributors within quality engineering (different level of seniority), by quality engineering managers, by development managers and project managers. Test cycles are run cross product (we currently run test cycles for about 5 apps, which spreads through about 12 teams; these are mostly mobile apps, however we run cycles also for browser certification testing).
1
Internally it's just me, who supports Applause. The others just request test cycles and evaluate incoming bugs.
It's just me who provides trainings, descriptions, scope, guidelines, etc. It took a while to figure out what level of detail Applause needs, which meant bigger time investment from my side. But now, it's significantly lower and Applause actually saves me plenty time.
Required skills: time management, planning
  • App release regression
  • New feature exploratory testing
  • Bug hunt
  • Bug hunt - when we are not able to find a bug reported from the field internally
  • New OS testing (for OS which were not released yet)
  • Using Applause's webinars and ebooks for internal trainings
  • Test automation
  • Security testing
  • Performance testing
The one missing point is for the price - it's quite expensive to maintain the service to the extent of how we use it (dozens of test cycles and hundreds of test case hours on monthly basis). However the benefits still weights the price, especially when thinking of the price of potential hot fixes. Still, the price can be a reason to take a look on how competition is doing.
No
  • Positive Sales Experience with the Vendor
During the time, the relationship never felt like vendor - customer only. I know that it's mostly about luck on the people you get to work with but maybe not. Maybe Applause really hire and train their employees in a way that they make you feel it matters. It's mostly the "friendly" relationship that makes Applause different from the other vendors.
It's still about spending money and getting the best value out of each dollar spent. By the time we were purchasing the service, there was no real competition to Applause (uTest at that time), therefore it was sort of a no brainer. If we would reconsider the whole contract, we would take on more competition.
  • Vendor implemented
No
Change management was minimal
We didn't really requested any changes so - nothing to report here.
  • Integration of the plugin that makes the transfer between applause and internal bug tracking system happening. it took time to make it seamlessly running.
I didn't need to be involved at all. It was seamless from our perspective. All products were inserted in by Vendor, only Test Cycles we needed to insert ourselves initially. Now even that is handled by Vendor. The only thing we need to pay attention now is - to request cycles at the right time and review the bugs found during the test cycles. Nothing else. Very good experience!
I know the score doesn't really correspond with my earlier answers, but I have really special relationship with the Applause people. I don't really go through official support. I rather use my internal connections to make my request handled as soon as possible - and it works really well! I don't need to go through the official channels. And it's known that the unofficial ones are much more effective. I can confirm!
No
Yep, it's when I wanted to change some default values for our integration plugin between the Applause platform and our internal bug tracking system. I didn't have to go through creating a ticket or reporting through Support at all. I just let our test lead know and he made the changes happen. Amazingly fast!
  • In the bug chat with the tester
  • Discussions
  • Browsing between bugs
  • Bug export
  • Bug search across projects
  • Switching products
  • Test cycle setup
Yes
I actually used it just couple times a while back, maybe in 2011 or 2012. It was such a horrible experience that I rather deleted the app and haven't tried it ever since. The bug browsing and approvals were really difficult, not even mentioning switching between products, which is not exactly easy within the web platform either. Forget the search.
The UI and the whole app is updated on regular basis, quite often actually. There are some cool features, like integration with several other bug tracking tools, which makes the bug management really easy. However there are some key usability issues within some of the less used workflows, which brings the score down a bit. They need to work on better switching between products and better bug search, especially across purchased products.
Return to navigation