Skip to main content

5 Principles to Guide Your Mobile Monitoring Decisions

Amir Rozenberg

Mobile is explosive in nature. It has been shown more than once that across verticals, it’s very expensive to be naïve as to the expected user adoption when it comes to mobile applications. You quickly come to realize you need to understand the behavior of the application in production.

Mobile monitoring is materially different from web monitoring, mainly due to the nature of the highly capable thick client. At the same time, the trends repeat: in the same way web monitoring quickly evolved to adopt the end user perspective through specific browsers and browser versions, also here, mobile monitoring is irrelevant if you’re not opting to adopt the end user perspective.

With that in mind, there are more than a few choices when coming to select your mobile monitoring solution. Here are some principles you want to keep in mind as you decide about your initial foray into this space.

1. Real Devices Matter

Adopt your end user perspective. This is a very simple, core principle. Browser emulation is equivalent to network monitoring. Imagine one user with iPhone 4S, and 10 applications running in the background. Another user with iPhone 6 and no applications running in the background. Will the server respond to both at the same time? Of course. Will the customer experience be the same? Absolutely not.

Further, commonly it’s not even possible to record and replay the calls from the device to the backend correctly. You almost need to recreate the application in your script, not to mention complex encryption that is usually applied to the backend calls. Long story short, if you’re not using what your users are seeing, you’re blind. It’s as simple as that.

2. Real devices drive triage

Are your existing tools able to provide you sufficient data about what happens on the application? With so much happening inside the thick client, you may want to understand the CPU and memory consumption when things go south. You will want to contrast this data across different devices, versions of the application, geographies and carriers. You will also want to have access to clean data that’s devoid of as much noise from the crowd, because it’s important for you to get to the root cause fast. We’ll come to it a bit later, but also your ability to extract UI elements will help you understand better what happened.

3. Know early

Probably the one thing you really want to avoid is seeing your brand showing in the media with the word "outage" next to it. The key is to know early there’s an issue and eliminate it quickly. To know early means that you can’t wait on your users to tell you: you need to proactively exercise the application and complete delivery chain frequently through the key user scenarios that are important. You want to setup and fine tune alerts that give you the information you need to be aware and act quickly.

4. Independence is key

If you made it this far down the article, you’re serious about finding a solution, and you need to show impact quickly. Going to the IT organization and asking them to install an agent inside the firewall to report metrics? Going to the developer and convincing them to embed a 3rd party SDK into the application? Maybe not the best strategy to achieve the desired outcome quickly. In fact, it’s commonly known that SDKs embedded into the application need to be looked at closely in terms of user privacy, application security and hit on the application performance. So much so that only 21% of developers integrate such SDKs into their application, according to Forrester.

The solution to gain insight into the end user experience quickly is via a SaaS solution that’s based on real devices and provides end-user perspective ongoing monitoring of the mobile application.

5. Continuous Integration schemas mandate insight ahead of launch

It’s no secret the mobile ecosystem is leading the "Shift-Left" paradigm change. With 2-week release cycles, there is no room for error, nor is there room for finding a performance issue just before going to production. Many organizations are breaking ground by monitoring the next release of the application based on the nightly build. This is a good measure to ensure there are no surprises on the launch of a new version of the application, perhaps even on new devices, such as iPhone 6, or new OS such as iOS8.

The practice of mobile monitoring is evolving the way people are used to think about monitoring. There are new users with challenging expectations, new people involved in monitoring (such as DevOps) and new tools. It’s important to pick the right tool to achieve insight into the application in production before your users share their frustration with friends and the media.

Amir Rozenberg is Director of Product Management for Perfecto Mobile.

Hot Topics

The Latest

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

5 Principles to Guide Your Mobile Monitoring Decisions

Amir Rozenberg

Mobile is explosive in nature. It has been shown more than once that across verticals, it’s very expensive to be naïve as to the expected user adoption when it comes to mobile applications. You quickly come to realize you need to understand the behavior of the application in production.

Mobile monitoring is materially different from web monitoring, mainly due to the nature of the highly capable thick client. At the same time, the trends repeat: in the same way web monitoring quickly evolved to adopt the end user perspective through specific browsers and browser versions, also here, mobile monitoring is irrelevant if you’re not opting to adopt the end user perspective.

With that in mind, there are more than a few choices when coming to select your mobile monitoring solution. Here are some principles you want to keep in mind as you decide about your initial foray into this space.

1. Real Devices Matter

Adopt your end user perspective. This is a very simple, core principle. Browser emulation is equivalent to network monitoring. Imagine one user with iPhone 4S, and 10 applications running in the background. Another user with iPhone 6 and no applications running in the background. Will the server respond to both at the same time? Of course. Will the customer experience be the same? Absolutely not.

Further, commonly it’s not even possible to record and replay the calls from the device to the backend correctly. You almost need to recreate the application in your script, not to mention complex encryption that is usually applied to the backend calls. Long story short, if you’re not using what your users are seeing, you’re blind. It’s as simple as that.

2. Real devices drive triage

Are your existing tools able to provide you sufficient data about what happens on the application? With so much happening inside the thick client, you may want to understand the CPU and memory consumption when things go south. You will want to contrast this data across different devices, versions of the application, geographies and carriers. You will also want to have access to clean data that’s devoid of as much noise from the crowd, because it’s important for you to get to the root cause fast. We’ll come to it a bit later, but also your ability to extract UI elements will help you understand better what happened.

3. Know early

Probably the one thing you really want to avoid is seeing your brand showing in the media with the word "outage" next to it. The key is to know early there’s an issue and eliminate it quickly. To know early means that you can’t wait on your users to tell you: you need to proactively exercise the application and complete delivery chain frequently through the key user scenarios that are important. You want to setup and fine tune alerts that give you the information you need to be aware and act quickly.

4. Independence is key

If you made it this far down the article, you’re serious about finding a solution, and you need to show impact quickly. Going to the IT organization and asking them to install an agent inside the firewall to report metrics? Going to the developer and convincing them to embed a 3rd party SDK into the application? Maybe not the best strategy to achieve the desired outcome quickly. In fact, it’s commonly known that SDKs embedded into the application need to be looked at closely in terms of user privacy, application security and hit on the application performance. So much so that only 21% of developers integrate such SDKs into their application, according to Forrester.

The solution to gain insight into the end user experience quickly is via a SaaS solution that’s based on real devices and provides end-user perspective ongoing monitoring of the mobile application.

5. Continuous Integration schemas mandate insight ahead of launch

It’s no secret the mobile ecosystem is leading the "Shift-Left" paradigm change. With 2-week release cycles, there is no room for error, nor is there room for finding a performance issue just before going to production. Many organizations are breaking ground by monitoring the next release of the application based on the nightly build. This is a good measure to ensure there are no surprises on the launch of a new version of the application, perhaps even on new devices, such as iPhone 6, or new OS such as iOS8.

The practice of mobile monitoring is evolving the way people are used to think about monitoring. There are new users with challenging expectations, new people involved in monitoring (such as DevOps) and new tools. It’s important to pick the right tool to achieve insight into the application in production before your users share their frustration with friends and the media.

Amir Rozenberg is Director of Product Management for Perfecto Mobile.

Hot Topics

The Latest

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...