Proudly building the #1 dating app for the LGBTQI+ Community
Find out how an efficient QA process can be key to the growth of a world-class company.
Not just a client,
but a standard for the people
If you tell anyone in the LGBTQI+ community that you are into dates, you will probably hear “Are you on Grindr?”.
This geosocial network has become one of the dating apps with the most users worldwide, and a pioneer in its class. By 2022 it already had 11 M monthly users and was listed on Wall Street with a valuation of $2.1 billion.
Devlane has been closely associated with Grindr from 2015, as a key player on a defining era. Between 2015 and 2018, as the app faced increasing challenges, Devlane built a team of 30+ engineers including QA engineers, Mobile developers, Backend engineers, and product managers, among other tech specialists involved in the process.
Our Laners adapted to the technologies previously used by Grindr, and carried out the process of researching, analyzing, choosing and developing more efficient and less expensive tech stacks.
faced by QA team
At the starting point, Grindr had not yet implemented any QA processes. They were at the time carrying out QA manual and automated client unit tests, but this only accounted for 15% test coverage.
While traffic was growing steadily, the photo moderation process was slow and inefficient, and the problem of spambot attacks was becoming more serious. Fake profiles tried to send ads, obtain sensitive information or convince the users to migrate to the competitors.
When we started working together, Grindr was on its way to stabilize the app with a team of 10 developers. At the time they were working on a rewrite of the backend’s code, but failures and crashes regularly occurred when attempting to deploy it to production.
The backend deployment process used to be traumatic because automated tests were unreliable. So time spent on manual testing was delaying releases, increasing the number of changes in each release.
There was also a structural problem: the code hadn’t aged well, so it was hard to add new features and updates.
Improvements made to their QA process
QA team built not just individual solutions, but parts of an ecosystem that could complement each other. It should be noted that the implementation would never have been possible without the agile and precise operation that we built between our and Grindr’s engineering team.
Efficient time management means a more profitable investment. The QA team understood this deeply, and their decisions reduced maintenance costs and testing time from hours to just minutes.