How to Manage Mobile App Development Complexity with Modern APM

Dave Hayes
Sentry

With a projected 7 billion mobile users by 2021, mobile is becoming the most dominant digital touchpoint for customer engagement. Annual mobile app downloads are projected to reach 258 billion by 2022 — a 45% increase from 2017. But downloads alone do not indicate mobile success — retention and engagement are key. While there are many factors that influence these metrics, application performance may be one of the most critical.

Application crashes can increase churn and damage brand reputation. In fact, app crashes cause more than 70% of uninstalls. Because Google ranking algorithms now downrank apps with stability problems, uptime and performance can even influence download metrics. It is imperative that organizations are delivering high-performing mobile applications and that the developers supporting those applications have the ability to identify and remediate errors efficiently.

But due to the growing complexity of the application ecosystem, this can be easier said than done. Developers are often limited by a lack of visibility and control over mobile devices. They have no way of knowing every device’s attributes or predicting which other apps and system processes may be competing for compute power. Mobile app developers are no strangers to segmentation faults and bus errors. And programming for such a diverse array of devices creates its own set of challenges. Flaws in native code, third-party dependencies or, in rare cases, even in the system libraries, can bring down the entire application.

Developers today are under pressure to deliver code faster than ever before. Even when rigorous testing processes are in place, the increasing complexity of application development will inevitably cause errors. Monitoring is an important component of application delivery, but the changing ecosystem calls for the reinvention of application performance monitoring that incorporates rich context and actionable insights.

Rethinking Application Performance Monitoring

While companies with faulty code are dealing with the fallout, those that rely on modern application performance monitoring (APM) are shipping better code more quickly and with less risk. Legacy monitoring tools focus more on system behavior, offering performance metrics on availability, throughput, and latency, but miss the mark when it comes to actionable insight that helps mobile developers make sense of complexity and quickly get to the root cause of errors.

On mobile — as with all native applications — it is important to have context beyond a crash. Developers need rich details supporting the error, such as the types of phones impacted, the number of users impacted, the specific actions a user took when the error was thrown, or even the storage capacity and battery life of the user's phone at the time the app crashed. These details are especially important for mobile developers because of the vast array of devices and native libraries used in programming. Having this information enables them to immediately triage and prioritize problems.

When developers can also identify the exact release and commit the error is tied to, they can quickly remediate the issue to minimize the breadth of impact. Developers can also move this feedback into the development cycle. By capturing every single exception and crash users encounter, meaningful trends will surface to help prioritize issues and avoid replication in future software release.

It is also important to consider that modern applications are not self-contained — they have multiple runtimes across the stack, causing added complexity in monitoring. Support for mobile, coupled with similar support for web, gives developers a complete picture, which is key in today’s application-centric landscape.

Innovation in the mobile space shows no signs of slowing, so developers must take proactive steps to address the factors that derail mobile app development and wreak havoc on user experience. By taking a modern approach to APM, incorporating rich context and actionable insights, and syncing this information across all of their applications, developers can code better and faster, ensuring their companies remain successful and competitive in the mobile world.

Dave Hayes is Head of Product at Sentry

Related Links

Hot Topics

The Latest

Beyond Buy vs. Build: The New Playbook for Data Pipelines

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

The Corporate Network Is Fading - Here's What Replaces It

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

IT Leaders Must Establish a Network Data Architecture Practice

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

Data Center Outages Are Decreasing but More Costly

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

Observability Has a Physical Layer Now: What AI Infrastructure Teaches IT Operations

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

TLS Certificate Expiration Is Becoming an Observability Problem

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprise Cloud Observability: Choosing the Right Starting Point

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

AI Is Making Incident Management More Complex - Bad Data Makes It Harder

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

MEAN TIME TO INSIGHT Podcast - Episode 26: Network Compliance

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Why VM and Container Monitoring Is Not Enough for Cloud-Hosted Autonomous Agents

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

How to Manage Mobile App Development Complexity with Modern APM

Dave Hayes
Sentry

With a projected 7 billion mobile users by 2021, mobile is becoming the most dominant digital touchpoint for customer engagement. Annual mobile app downloads are projected to reach 258 billion by 2022 — a 45% increase from 2017. But downloads alone do not indicate mobile success — retention and engagement are key. While there are many factors that influence these metrics, application performance may be one of the most critical.

Application crashes can increase churn and damage brand reputation. In fact, app crashes cause more than 70% of uninstalls. Because Google ranking algorithms now downrank apps with stability problems, uptime and performance can even influence download metrics. It is imperative that organizations are delivering high-performing mobile applications and that the developers supporting those applications have the ability to identify and remediate errors efficiently.

But due to the growing complexity of the application ecosystem, this can be easier said than done. Developers are often limited by a lack of visibility and control over mobile devices. They have no way of knowing every device’s attributes or predicting which other apps and system processes may be competing for compute power. Mobile app developers are no strangers to segmentation faults and bus errors. And programming for such a diverse array of devices creates its own set of challenges. Flaws in native code, third-party dependencies or, in rare cases, even in the system libraries, can bring down the entire application.

Developers today are under pressure to deliver code faster than ever before. Even when rigorous testing processes are in place, the increasing complexity of application development will inevitably cause errors. Monitoring is an important component of application delivery, but the changing ecosystem calls for the reinvention of application performance monitoring that incorporates rich context and actionable insights.

Rethinking Application Performance Monitoring

While companies with faulty code are dealing with the fallout, those that rely on modern application performance monitoring (APM) are shipping better code more quickly and with less risk. Legacy monitoring tools focus more on system behavior, offering performance metrics on availability, throughput, and latency, but miss the mark when it comes to actionable insight that helps mobile developers make sense of complexity and quickly get to the root cause of errors.

On mobile — as with all native applications — it is important to have context beyond a crash. Developers need rich details supporting the error, such as the types of phones impacted, the number of users impacted, the specific actions a user took when the error was thrown, or even the storage capacity and battery life of the user's phone at the time the app crashed. These details are especially important for mobile developers because of the vast array of devices and native libraries used in programming. Having this information enables them to immediately triage and prioritize problems.

When developers can also identify the exact release and commit the error is tied to, they can quickly remediate the issue to minimize the breadth of impact. Developers can also move this feedback into the development cycle. By capturing every single exception and crash users encounter, meaningful trends will surface to help prioritize issues and avoid replication in future software release.

It is also important to consider that modern applications are not self-contained — they have multiple runtimes across the stack, causing added complexity in monitoring. Support for mobile, coupled with similar support for web, gives developers a complete picture, which is key in today’s application-centric landscape.

Innovation in the mobile space shows no signs of slowing, so developers must take proactive steps to address the factors that derail mobile app development and wreak havoc on user experience. By taking a modern approach to APM, incorporating rich context and actionable insights, and syncing this information across all of their applications, developers can code better and faster, ensuring their companies remain successful and competitive in the mobile world.

Dave Hayes is Head of Product at Sentry

Related Links

Hot Topics

The Latest

Beyond Buy vs. Build: The New Playbook for Data Pipelines

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

The Corporate Network Is Fading - Here's What Replaces It

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

IT Leaders Must Establish a Network Data Architecture Practice

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

Data Center Outages Are Decreasing but More Costly

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

Observability Has a Physical Layer Now: What AI Infrastructure Teaches IT Operations

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

TLS Certificate Expiration Is Becoming an Observability Problem

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprise Cloud Observability: Choosing the Right Starting Point

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

AI Is Making Incident Management More Complex - Bad Data Makes It Harder

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

MEAN TIME TO INSIGHT Podcast - Episode 26: Network Compliance

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Why VM and Container Monitoring Is Not Enough for Cloud-Hosted Autonomous Agents

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...