Skip to main content

How to Avoid Mobile Application Meltdown

Mobile Computing: A Whole New Approach to APM

Consumer mobile apps are everywhere, but many CIOs are just beginning to consider how to best distribute mobile apps to workers and customers. Companies with more progressive outlooks are developing their own internal app stores, and analyzing which legacy apps should go mobile and which third-party apps to support. In the rush to meet the needs of the business, and keep pace with demands from customers and partners who crave mobile access, IT risks making some missteps.

The consumer IT movement means that expectations for performance have changed dramatically. Developers and IT managers need to understand the requirements for “instant-on” apps, which launch at the touch of a finger and work flawlessly all the time. If an application stops working, the user will ditch it and go download something else. So what can you do to avoid mobile application meltdown and failed ROI?

Performance in the Mobile World

There are many differences between mobile, distributed computing and computing of the past -- in which users and applications were tethered to the desktop. For one, most enterprise IT departments have limited visibility beyond servers.

In the mobile world, IT needs to determine how to efficiently and accurately trace the transaction to a single user’s device -- no matter whether the device runs Android, Apple iOS, Windows or something else. That requires a new approach to monitoring, and possibly, new tools and processes based on user-centric experiences. From the narrow angle of the server side performance, response times may seem peachy. In reality, due to inefficient website implementation (e.g. multiple roundtrips) or a slow network, users may suffer.

Then IT must consider the vast number of different locations from where users will be accessing corporate data and applications on their mobile devices. The more variability -- users who log on from home, the airport, over corporate or public cloud connections -- the more complicated troubleshooting will be for the IT team. Also, IT has a higher incidence of unexpected use patterns, as more people log on during unpredictable hours and from unknown locations.

With so many different potential issues and devices to monitor, not to mention higher volumes of traffic altogether, a sophisticated alert system based on historical trend analysis will help IT stay in the driver’s seat.

What is the threshold for each device and operating system, after which performance will likely begin to suffer? How do certain geographic regions and common user locations (e.g. metropolitan airports) differ from others when it comes to performance and network reliability? Alerts should be customized for a much larger number of potential situations and scenarios so that IT can respond appropriately -- versus a costly and ineffective one-size-fits-all approach.

Website and IT managers need to consider how well their public and private sites are optimized for mobile access. Many enterprise applications today, particularly legacy ones, don’t run well from the mobile Web. Best coding practices for supporting mobile clients include minimizing the number of “round trips” or the requests from client to server such as client-side redirection and loading only the content that the user needs to see right now, often called “lazy loading”.

Finally, application managers will need to develop and monitor a much larger number of performance baselines. Most organizations are supporting multiple different platforms across the user base. This means that there is no such thing anymore as a single transaction baseline, related to a hardwired PC. To compare apples to apples, application monitoring must be segmented by network and platform (e.g. LAN user, WiFi user, teleworker, mobile user by device) so when things go wrong you can locate exactly the problem spot.

In our mobile world, maintaining the status quo for application performance isn’t viable. Employees and customers now have much more power when it comes to information technology. Enterprise mobile computing is bound to have vast and still unknown implications on the practice of application performance management. Yet being proactive with a mobile APM strategy can deliver a whole new level of business productivity and innovation to delight employees and end customers alike.

About Zohar Gilad

Zohar Gilad is Executive Vice President, Products, Marketing and Channels at Precise Software. Before joining Precise, Zohar held several senior executive positions with Mercury Interactive, acquired by HP in 2006. At Mercury, Zohar drove expansion into new markets, creating new product categories: Load Testing, Quality Management, Application Management, and finally Business Technology Optimization. From 2000-2003, as the General Manager of the Application Management business unit, he helped grow the business from $0 to about $100M a year. Prior to joining Mercury, Zohar held software development positions at IBM and Daisy Systems.

Related Links:

www.precise.com

The Latest

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 ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

How to Avoid Mobile Application Meltdown

Mobile Computing: A Whole New Approach to APM

Consumer mobile apps are everywhere, but many CIOs are just beginning to consider how to best distribute mobile apps to workers and customers. Companies with more progressive outlooks are developing their own internal app stores, and analyzing which legacy apps should go mobile and which third-party apps to support. In the rush to meet the needs of the business, and keep pace with demands from customers and partners who crave mobile access, IT risks making some missteps.

The consumer IT movement means that expectations for performance have changed dramatically. Developers and IT managers need to understand the requirements for “instant-on” apps, which launch at the touch of a finger and work flawlessly all the time. If an application stops working, the user will ditch it and go download something else. So what can you do to avoid mobile application meltdown and failed ROI?

Performance in the Mobile World

There are many differences between mobile, distributed computing and computing of the past -- in which users and applications were tethered to the desktop. For one, most enterprise IT departments have limited visibility beyond servers.

In the mobile world, IT needs to determine how to efficiently and accurately trace the transaction to a single user’s device -- no matter whether the device runs Android, Apple iOS, Windows or something else. That requires a new approach to monitoring, and possibly, new tools and processes based on user-centric experiences. From the narrow angle of the server side performance, response times may seem peachy. In reality, due to inefficient website implementation (e.g. multiple roundtrips) or a slow network, users may suffer.

Then IT must consider the vast number of different locations from where users will be accessing corporate data and applications on their mobile devices. The more variability -- users who log on from home, the airport, over corporate or public cloud connections -- the more complicated troubleshooting will be for the IT team. Also, IT has a higher incidence of unexpected use patterns, as more people log on during unpredictable hours and from unknown locations.

With so many different potential issues and devices to monitor, not to mention higher volumes of traffic altogether, a sophisticated alert system based on historical trend analysis will help IT stay in the driver’s seat.

What is the threshold for each device and operating system, after which performance will likely begin to suffer? How do certain geographic regions and common user locations (e.g. metropolitan airports) differ from others when it comes to performance and network reliability? Alerts should be customized for a much larger number of potential situations and scenarios so that IT can respond appropriately -- versus a costly and ineffective one-size-fits-all approach.

Website and IT managers need to consider how well their public and private sites are optimized for mobile access. Many enterprise applications today, particularly legacy ones, don’t run well from the mobile Web. Best coding practices for supporting mobile clients include minimizing the number of “round trips” or the requests from client to server such as client-side redirection and loading only the content that the user needs to see right now, often called “lazy loading”.

Finally, application managers will need to develop and monitor a much larger number of performance baselines. Most organizations are supporting multiple different platforms across the user base. This means that there is no such thing anymore as a single transaction baseline, related to a hardwired PC. To compare apples to apples, application monitoring must be segmented by network and platform (e.g. LAN user, WiFi user, teleworker, mobile user by device) so when things go wrong you can locate exactly the problem spot.

In our mobile world, maintaining the status quo for application performance isn’t viable. Employees and customers now have much more power when it comes to information technology. Enterprise mobile computing is bound to have vast and still unknown implications on the practice of application performance management. Yet being proactive with a mobile APM strategy can deliver a whole new level of business productivity and innovation to delight employees and end customers alike.

About Zohar Gilad

Zohar Gilad is Executive Vice President, Products, Marketing and Channels at Precise Software. Before joining Precise, Zohar held several senior executive positions with Mercury Interactive, acquired by HP in 2006. At Mercury, Zohar drove expansion into new markets, creating new product categories: Load Testing, Quality Management, Application Management, and finally Business Technology Optimization. From 2000-2003, as the General Manager of the Application Management business unit, he helped grow the business from $0 to about $100M a year. Prior to joining Mercury, Zohar held software development positions at IBM and Daisy Systems.

Related Links:

www.precise.com

The Latest

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 ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...