Your customers expect your mobile applications to work, every time. You need to see performance problems and end-user experiences in real-time and understand what might be affecting your application’s performance.
New Relic Mobile allows you to monitor and manage the performance of your iOS and Android applications by providing end-to-end details, errors, and throughput from every angle in real time. To help you be as successful as possible with Mobile, we’ve put together a list of best practices that will keep you organized and help you take action.
When you have reviewed these best practices, show off your new found skills. Take the Mobile Best Practices Quiz to earn your badge .
Create a naming schema for your applications
You could have a large number of applications, with multiple OS versions. Making sure you can find the right app when you get alerted is crucial to reducing the time it takes to resolve your issue. Create a naming scheme like:
OS (iOS/Android) - AppName - Environment (Prod/Dev/QA/Staging) to help locate your applications quicker, when you need it most.
Keep your apps up to date.
The frequency at which mobile technology changes can be overwhelming. One of the first steps in troubleshooting issues with mobile apps reporting to New Relic, is to verify you are using a recent version of the Mobile agent. Each release contains bug fixes and more support for additional features. Making sure you are up to date is a great way to ensure you are getting the best, most accurate reports in New Relic.
- NRQL to see the versions of the Mobile Agent used
- Android Agent Release Notes
- iOS Agent Release Notes
Understanding your data
Interpret your Crash Reports
Symbolicated crashes are those which have had words/symbols associated with memory addresses. By default, iOS provides Symbolicated crash reports. Android uses Proguard/Dexguard to Symbolicate it’s crash reports. You’ll need to de-obfuscate your crash reports to understand the root cause. New Relic uses iOS dSYM files and Android Mapping files to de-obfuscate those crash reports. Understanding how to use these files is key to interpreting your crash reports.
Find Third Party Service Slowdowns
Mobile applications depend on multiple APIs and external services. We see this most frequently in the “Login with ‘3rd party service’” button that we see in most mobile apps. A large number of mobile applications depend on services like Google Maps as well. Each service that your application depends on adds another potential point of failure, and another service with the power to slow down your application’s performance. Using the HTTP Requests page in New Relic Mobile, you’ll see a breakdown of the requests being made in your app, where you can analyse the performance of these requests.
Taking action on your data
Capture custom data
The New Relic Mobile Agents captures a wide variety of data by default - you can see a list here - and this list is extendable with custom events. Using custom events you can track anything from specific user actions, to individual purchases in your app.
Trace crashes with the event trail and breadcrumb events
Sometimes you have to understand the customer’s path through the application to know why a crash happened. The event trail in Mobile shows each interaction made in the app for a given occurrence of a crash. You can include any further breakpoints for monitoring, such as Breadcrumb events. These show up in the event trail to help you more quickly troubleshoot your app crashes.
Ready to learn more?
Looking for more Mobile best practices and tips? Check out the Mobile Level Up category .