RunKeeper Scales to Meet Demand from 24 Million Global Users with New Relic

When Apple first introduced the App Store in 2008, RunKeeper was one of its first sellers. RunKeeper’s mobile fitness app helped introduce the world to the capabilities of the smartphone by allowing users to access a ‘personal trainer in your pocket.’ Customers can track their runs, fitness goals, and measure their progress while on the go. Today, more than 24 million global customers use the app on Android and iOS devices. But scaling to meet this expansive user base wasn’t always easy.

 logo-login

In the early days of RunKeeper’s growth, the company found that scaling quickly produced application performance challenges, so it turned to New Relic for comprehensive monitoring of its servers and mobile apps. With New Relic’s Server Monitoring, the team was able to solve its server-scaling issues and understand where the bottlenecks were, right down to the line of code.

Although RunKeeper already had a suite of mobile tools (Crashlytics, Google Analytics, Monit, Pingdom) in place, they were not getting the proactive insight they needed. So when New Relic for Mobile Apps was announced, RunKeeper jumped on the opportunity to gain deeper insight into their customers’ mobile experience. New Relic for Mobile Apps augments RunKeeper’s existing toolset, providing an end-to-end view into performance while reducing operational costs.

Working in an agile environment with up to 10 deployments daily, New Relic allows RunKeeper to make releases with confidence. “New Relic for Mobile Apps helps us understand exactly how many users are being affected by any given issue,” says Joe Bondi, Co-Founder and CTO at RunKeeper.  “Once we address the problem at hand, we can see right away — within hours or even minutes — whether or not the changes worked. It takes the guesswork out of identifying and fixing issues in production.”

runkeeper       runkeeper2      

Before RunKeeper had New Relic for Mobile Apps, the team could only see the web application side of things. They knew when the phones were hitting their server, but not much else. “Now we have deep insight into network connectivity failures that were invisible to us before — for example, issues around DNS, SSL and HAProxy connections,” says Bondi. “It’s like we’re finally looking at the complete picture for the first time.”

READ THE FULL CASE STUDY
Read the full case study to find out how New Relic helps RunKeeper meet demand from millions of global end-users to help them maximize their fitness goals.

desdemona@newrelic.com'

View posts by .

Interested in writing for New Relic Blog? Send us a pitch!