Skip to main content

Poor User Experience - Leading Cause of Enterprise Mobile App Failures

Pete Goldin
APMdigest

A traditional approach to mobile application development for enterprises causes friction and misalignment between developers and designers, with 50 percent of respondents saying their projects fail to lock or get approved because of user interface issues, according to Bridging the Gap: Mobile App Design and Development, a survey from Kony covering enterprise mobility app designer and developers.

The survey of more than 340 respondents from leading global brands reveals a gap in the mobile app design and development process specifically when it comes to user interface and user experience. Per Kony, this user interface gap and rework are the causes for many change requests, which lead to project delays and poor user adoption.

“Today’s IT departments are struggling to keep pace with the demands of their business to mobilize their enterprise,” said Dave Shirk, Kony EVP and CMO. “CIOs are faced with the challenge of rapidly delivering mobile applications for their businesses, and this survey sheds light on one of the biggest hurdles: business users, designers and developers don’t see eye to eye when it comes to user experience and interface design, which can cause costly delays and mobile app failures, leaving the business looking for a better answer.”

Key findings:

■ User interface is the main source of frustration: Developers said the three main reasons for changes to the user interface are because the user interface design never gets locked; the stakeholder identified issues in the user interface once they got to use the working application; and the user interface design failed to address one or more functional requirements.

■ Change requests slow down development time: More than half of developers said that 25 to 75 percent of their projects receive change requests that impact the user interface. Moreover, nearly 40 percent of developers said it takes 25 to 50 percent of additional development effort to address change requests that impact the user interface. Approximately a third said it requires 50 to 100 percent more effort for development projects, and nearly five percent said change requests more than double the original development effort required.

■ Developers struggle with user interface and user experience: Designers cited communicating input back to developers on the mobile app prototype and successful collaboration with the developer during the development cycle as the most challenging aspects of working with their developer team to seamlessly create engaging mobile apps.

“To ensure mobile app success, businesses should take a holistic approach to mobile app development,” continued Shirk. “In the world of mobile, the software development lifecycle needs to begin with design. Mobile app design is often overlooked in the development process, but companies are finding that most mobile apps fail because of lack of user adoption caused by poor design and experience. Enterprises should design their app with a mobile perspective when it comes to look and feel of the app. Doing this in a collaborative way and leveraging cloud technology is far better than the classic design tools, which have zero functionality or relevance to support the rich and varied user experience requirements of mobile technology.”

Pete Goldin is Editor and Publisher of APMdigest

Hot Topics

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...

Poor User Experience - Leading Cause of Enterprise Mobile App Failures

Pete Goldin
APMdigest

A traditional approach to mobile application development for enterprises causes friction and misalignment between developers and designers, with 50 percent of respondents saying their projects fail to lock or get approved because of user interface issues, according to Bridging the Gap: Mobile App Design and Development, a survey from Kony covering enterprise mobility app designer and developers.

The survey of more than 340 respondents from leading global brands reveals a gap in the mobile app design and development process specifically when it comes to user interface and user experience. Per Kony, this user interface gap and rework are the causes for many change requests, which lead to project delays and poor user adoption.

“Today’s IT departments are struggling to keep pace with the demands of their business to mobilize their enterprise,” said Dave Shirk, Kony EVP and CMO. “CIOs are faced with the challenge of rapidly delivering mobile applications for their businesses, and this survey sheds light on one of the biggest hurdles: business users, designers and developers don’t see eye to eye when it comes to user experience and interface design, which can cause costly delays and mobile app failures, leaving the business looking for a better answer.”

Key findings:

■ User interface is the main source of frustration: Developers said the three main reasons for changes to the user interface are because the user interface design never gets locked; the stakeholder identified issues in the user interface once they got to use the working application; and the user interface design failed to address one or more functional requirements.

■ Change requests slow down development time: More than half of developers said that 25 to 75 percent of their projects receive change requests that impact the user interface. Moreover, nearly 40 percent of developers said it takes 25 to 50 percent of additional development effort to address change requests that impact the user interface. Approximately a third said it requires 50 to 100 percent more effort for development projects, and nearly five percent said change requests more than double the original development effort required.

■ Developers struggle with user interface and user experience: Designers cited communicating input back to developers on the mobile app prototype and successful collaboration with the developer during the development cycle as the most challenging aspects of working with their developer team to seamlessly create engaging mobile apps.

“To ensure mobile app success, businesses should take a holistic approach to mobile app development,” continued Shirk. “In the world of mobile, the software development lifecycle needs to begin with design. Mobile app design is often overlooked in the development process, but companies are finding that most mobile apps fail because of lack of user adoption caused by poor design and experience. Enterprises should design their app with a mobile perspective when it comes to look and feel of the app. Doing this in a collaborative way and leveraging cloud technology is far better than the classic design tools, which have zero functionality or relevance to support the rich and varied user experience requirements of mobile technology.”

Pete Goldin is Editor and Publisher of APMdigest

Hot Topics

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...