Introduction to mobile monitoring

New Relic's mobile monitoring capabilities help you gain deeper visibility into how to analyze your Android and iOS application performance and troubleshoot crashes. You can also examine HTTP and other network performance for unexpected lag, which will in turn help you collaborate more efficiently with your backend teams.

To use mobile monitoring and the rest of our observability platform, join the New Relic family! Sign up to create your free account in only a few seconds. Then ingest up to 100GB of data for free each month. Forever.

How we use mobile monitoring

At New Relic, we have our own mobile developers who create iOS and Android apps so our customers can use New Relic from their mobile devices. During a feature deploy, we encountered a small bug that caused an edge case crash with our Android app. This happened after we had created, tested, and deployed the new feature.

Because we work at New Relic, we also use New Relic One to analyze and troubleshoot our mobile apps. To give you an idea of how to explore the power of mobile monitoring, here's an example of how our own mobile engineers used it to track this small bug.

Crash analysis workflow with New Relic Mobile
A workflow to identify and resolve mobile app crashes using New Relic.
1. Alert notification shows new version crashes

The night after a new release, our on-call developer received an alert notification on his mobile phone. The Alerts page indicated that some customers were seeing crashes on the new version of our Android app.

Moving to his desktop browser, he checked the Summary page. The overview showed an increase in crashes for the newest version. By filtering for the latest version and setting the time picker to the past 24 hours, he could proceed with crash analysis.

New Relic One: Mobile summary
An example of using the mobile Summary page to filter to an Android version with crashes.
2. Crash analysis pinpoints exception, location, and more

By clicking the Crashes chart title on the mobile Summary page, the Crash analysis page opened with the same 24-hour time frame and filter to this Android version. Here our developer could see a significant number of crashes for the selected version. This reinforced his suspicion there was bad code somewhere in the recent deployment.

The developer clicked the link for the crash type to examine the exception, location, and error message. He also examined the stack trace, interaction trail, and event trail to quickly understand where users were impacted.

New Relic One: Mobile crash analysis
An example of using the Crash analysis page to track down the cause for crashes for a new release by examining the exception, location, and error message.

From here the developer saw the error. The new feature had a specific line of bad code that was crashing the app for customers who only used New Relic to monitor one app rather than multiple apps. The team released a hot fix in less than an hour, and the crash rate quickly de-escalated to 0.2%.

3. Problem solved, focus on improving app performance

The problem was solved, but the team continues to use New Relic to make sure the most important workflows are running correctly and quickly. We also share HTTP and other network performance trends with our backend API developer teams.

Improve frontend and backend performance

More than a tool for crash analysis, our mobile monitoring capabilities can help you identify opportunities to speed app performance. For example, you can:

And more!

Do more with New Relic Mobile
In addition to crash analysis, do more to fine-tune mobile app performance.

Great mobile apps increasingly rely on backend systems to power their functionality, such as requesting product information, authenticating users, or streaming media content. But some backend issues can lead to upstream mobile app crashes, freezes, and broken functionality that impacts end users, including:

  • Changed or non-versioned API endpoints
  • Bad payloads
  • API timeouts
  • Slow or deprecated API endpoints

You can use the network pages in our mobile monitoring UI to identify problems that surface through HTTP requests, errors, and other network issues. You can also query your data. Then create dashboards and share this information with backend API developer teams and others in your organization to help improve the overall end user experience with your mobile app.

You can also improve your customers' overall digital experience:

  • Get rapid visibility into how your end users experience your mobile apps and web browsers.
  • Analyze actual or simulated end-user behavior to hone in on metrics like load time, availability, and errors, while staying grounded in the backend services that enable these digital experiences.

Get started with mobile monitoring

Before you install and configure New Relic's functionality for your mobile applications, follow these guidelines for compatibility and other requirements:

Then continue with the installation and configuration procedures for your Android, iOS, tvOS, or Cordova application.

For more help

If you need more help, check out these support and learning resources: