Most forward-looking brands today are using an Application Performance Management (APM) tool to help monitor the health of their mobile apps. APM tools allow developers to monitor crashes, errors and the speed of network requests. Most APM tools will also allow you to segment data by attributes such as app version, or end users’ OS version, to allow deeper understanding of problems that might be occurring within the app.
The Neumob Portal already surfaces best-in-class mobile metrics surrounding the speed of network requests, as well as in-app errors by country, domain, mobile network and much more. We’ve found that many Neumob customers like to additionally validate the impressive acceleration gains they’re seeing within our portal by also using a third-party APM tool, and one of the most popular is New Relic’s.
Let’s look at the best methods to read and interpret the improvements Neumob is making in speeding network requests and reducing errors by using New Relic.
New Relic supports the uploading of custom mobile events within the New Relic SDK to be used within the “Insights” feature within the app. Unfortunately when using “Insights” and executing data queries, some of the most important metrics that help an app owner understand the impact Neumob is having on performance aren’t readily available.
To help with the problem above, New Relic allows a developer to overwrite the “Application Version”. By default, New Relic gets the app version from either the AndroidManifest.xml or build.gradle file on Android or the value in “CFBundleShortVersionString” for iOS.
Neumob recommends that developers interested in understanding the impact Neumob is having on performance and error reduction use this method within New Relic to capture a custom application version: If the user is being accelerated by Neumob, simply append the letter ‘N’ to the existing application version.
Once you’ve updated the application version within the app, New Relic has a suite of reports that compare app versions against each other. To find these, navigate to the “Mobile” tool, and select “Versions”, which is located under the “Usage” sub-heading.
Here you’ll be presented with 5 reports: “Interaction Time”, “Network Failure Rate”, “Average Response Time”, “App Launches” and “Average Memory Used”.
To best understand the impact Neumob is providing to your app (and your app’s users around the world), we recommend taking a close look at both “Average Response Time” and “Network Failure Rate”.
Below, we give an example of how to update the application version within the New Relic SDK.
NewRelic.withApplicationVersion(‘currentAppVersion + “N”’)
[NewRelic setApplicationVersion:(NSString*) currentAppVersion + “N”];
NewRelic.setApplicationVersion(currentAppVersion + “N”)
Hopefully this is helpful to you in measuring and validating the performance of your app using the Neumob SDK – and we’re certainly available to help answer any questions you might have via our Support pages or by emailing us right here.