4 Differences Between Mobile and Server Performance Monitoring
October 15, 2014
Ofer Ronen
Share this

According to eMarketer, as of 2014 Americans consume more media using mobile devices than laptops and desktops combined. This shift in consumer behavior is also occurring within corporations, as employees increasingly rely on mobile devices for their work.

With such a surge in mobile usage there is a growing need for corporations to ensure that their mobile experience is high quality and not broken.

Since 86% of mobile experiences occur within apps and not mobile browsers [source: Flurry], focusing on improving app performance has a larger impact on mobile quality.

The following are 4 key differences that companies monitoring their server (and website) performance should consider when selecting a mobile app performance monitoring solution.

1. Different Team, Different Needs

At most companies, mobile teams are not part of the server/website teams. Instead mobile teams are completely separate and in many cases they are an outsourced team.

The mobile teams have unique pain points when releasing mobile apps that are different from those of web and backend developers (more on this below). Solutions that slightly tweak the interface of a server performance monitoring service do not cut it. These teams require solutions designed from the ground up to solve their problems.

2. Scaling vs. Fragmentation Challenge

Developers on server teams face scaling problems. When a website or backend developer writes a line of code they need to ensure that it performs well as traffic grows and lots of users hit that code.

On the other hand developers on mobile teams face fragmentation problems. When a mobile developer writes a line of code they need to ensure that it will run well on thousands of device configurations, including varying device types, connection types, and OS versions.

A recent study by OpenSignal found that there are over 18,000 types of Android devices. How does a mobile developer confirm that their app code doesn’t break across all these devices? There is only one way, monitor production performance using a service that makes it easy to slide and dice the live performance.

3. Network vs. Device Performance

Server teams are primarily concerned with network performance. When the network is slow the bits don’t get downloaded to the thin client, usually a browser, and the end user suffers.

Mobile teams however are concerned with much more than just the network performance; they are dealing with low-end devices running their evolving client code base.

Unique challenges for mobile app developers include:

- How smooth are the interactions (e.g. scrolling)?

- Are apps hitting memory limits on certain devices hurting the user experience?

- Are users on lower end devices waiting an unreasonable amount of time for calculations to finish?

- Is the app draining the battery at an unreasonable rate?

A performance solution for mobile developers needs to be much more comprehensive in the type of metrics captured, and go beyond simply reporting on network issues.

4. Greater Variability of User Experiences

Unlike desktops and laptops, which are high-powered devices often used indoors on reliable networks, mobile devices have more chaotic environments with a wide range of capabilities running on top of unreliable networks.

Since mobile has more variability, performance monitoring solutions need to remove noise from the data to make it usable. For example, the ability to slice and dice the data to view the data that matters, like performance in the US of the latest app version on older but popular handsets.

Mobile performance monitoring solutions should also provide the ability to handle noise introduced by outliers that distort the average performance. This can be addressed by metrics like 95th percentile performance, which are more representative of a slow experience, and 50th percentile performance, to better measure the typical experience.

Finally, noise is created by interrupted app sessions like answering a phone call in the middle of a session. Solutions that detect and handle interruptions present a clearer picture of true performance.


As users migrate to using mobile apps, businesses face a challenge ensuring the same high quality experiences provided on the Web. In selecting a mobile performance monitoring service to help discover and prioritize outstanding issues, businesses should consider the unique pain points their mobile teams face as outlined above.

ABOUT Ofer Ronen

Ofer Ronen is the Co-founder and CEO of Pulse.io, a performance monitoring service for mobile app developers. The service monitors over 400 monthly sessions for companies of all sizes. It is unique in the level of performance metrics reported, ensuring that issues are not missed. Ronen previously was CEO of Sendori (sold to IAC), a mobile and web ad network. He received a computer engineering MS/BS from Michigan, and MBA from Cornell.

Share this

The Latest

November 14, 2019

A brief introduction to Applications Performance Monitoring (APM), breaking it down to a few key points, followed by a few important lessons which I have learned over the years ...

November 13, 2019

Research conducted by ServiceNow shows that Gen Zs, now entering the workforce, recognize the promise of technology to improve work experiences, are eager to learn from other generations, and believe they can help older generations be more open‑minded ...

November 12, 2019

We're in the middle of a technology and connectivity revolution, giving us access to infinite digital tools and technologies. Is this multitude of technology solutions empowering us to do our best work, or getting in our way? ...

November 07, 2019

Microservices have become the go-to architectural standard in modern distributed systems. While there are plenty of tools and techniques to architect, manage, and automate the deployment of such distributed systems, issues during troubleshooting still happen at the individual service level, thereby prolonging the time taken to resolve an outage ...

November 06, 2019

A recent APMdigest blog by Jean Tunis provided an excellent background on Application Performance Monitoring (APM) and what it does. A further topic that I wanted to touch on though is the need for good quality data. If you are to get the most out of your APM solution possible, you will need to feed it with the best quality data ...

November 05, 2019

Humans and manual processes can no longer keep pace with network innovation, evolution, complexity, and change. That's why we're hearing more about self-driving networks, self-healing networks, intent-based networking, and other concepts. These approaches collectively belong to a growing focus area called AIOps, which aims to apply automation, AI and ML to support modern network operations ...

November 04, 2019

IT outages happen to companies across the globe, regardless of location, annual revenue or size. Even the most mammoth companies are at risk of downtime. Increasingly over the past few years, high-profile IT outages — defined as when the services or systems a business provides suddenly become unavailable — have ended up splashed across national news headlines ...

October 31, 2019

APM tools are ideal for an application owner or a line of business owner to track the performance of their key applications. But these tools have broader applicability to different stakeholders in an organization. In this blog, we will review the teams and functional departments that can make use of an APM tool and how they could put it to work ...

October 30, 2019

Enterprises depending exclusively on legacy monitoring tools are falling behind in business agility and operational efficiency, according to a new study, Prevalence of Legacy Tools Paralyzes Enterprises' Ability to Innovate conducted by Forrester Consulting ...

October 29, 2019

Hyperconverged infrastructure is sometimes referred to as a "data center in a box" because, after the initial cabling and minimal networking configuration, it has all of the features and functionality of the traditional 3-2-1 virtualization architecture (except that single point of failure) ...