Foi então que a Gameloft encontrou o Firebase Crashlytics. Agregando as falhas por causa e se concentrando no impacto para os jogadores, o Crashlytics ajudou a Gameloft a ver o que precisava ser corrigido antes: algo especialmente útil devido ao alto número de jogos que a empresa precisa gerenciar. "Com o Crashlytics, é fácil analisar stack traces. Ele ajuda a priorizar problemas e apresenta informações importantes sobre cada bug", conta Radulescu. "Os registros e chaves foram usados para descobrir detalhes e contextualizar as falhas, por exemplo, definindo a pista ou carro afetado em um jogo de corrida, para que possamos reproduzir e resolver o problema mais rápido do que nunca."

When one of their games, Overdrive City, was suffering from mysterious crashes, the team received a velocity alert, warning them that the issue had increased in severity. Thanks to the alert, the Gameloft team swiftly took action and found the culprit — a malfunctioning ad module — and temporarily deactivated it while they fixed the problem, reducing the percentage of users experiencing crashes by 10% overnight. Players appreciated the quick fix. According to Gameloft, in the subsequent weeks, crashes remained low, the game's Play Store rating went up, and session duration increased by 16%, from 6 minutes to 7 minutes. Since then, Crashlytics has become an integral part of Gameloft's ability to monitor stability, roll out features with confidence, and keep players happy.