DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations

Why Mobile App Projects Fail and How to Make Sure They Succeed

Most of the time when a mobile app doesn't do as well as hoped, its nothing wrong with the app itself, but rather the company's processes, such as usability testing.

Amy Groden-Morrison user avatar by
Amy Groden-Morrison
·
Mar. 16, 17 · Opinion
Like (0)
Save
Tweet
Share
4.35K Views

Join the DZone community and get the full member experience.

Join For Free

Sad but true: Many projects for building mobile apps fail, and the cause isn’t that companies don’t have sufficient resources. It’s that their process for building mobile apps is essentially built for failure. So concludes a survey from IDG, Top CIO Challenges that Contribute to Enterprise Application Failure. Following is an explanation of why mobile apps fail – and what companies can do to make sure they succeed.

Why Mobile Apps Fail

The survey makes clear that mobile apps are high on enterprises’ must-do lists: 75% of executives surveyed said mobility is a moderate, high, or critical priority for their organizations. Not surprisingly, 60% of the executives said that usability is key to the success of mobile apps. In addition, 42% of respondents in large organizations said that a good user experience is a major contributor to whether a mobile app is adopted by people in their organization.

Simply accomplishing an objective is no longer enough. Now user experience and ease of use are also critical for success.

The survey notes that “With the consumerization of IT and the increase in mobile computing, the user is much more critical to the development process. Ten years ago, a poor user experience wouldn’t doom a project. As long as the application did what it was supposed to do, it was considered a success.”

That’s no longer the case, though, because the survey found that “Internal and external users of applications have very high expectations for usability and functionality. Simply accomplishing an objective is no longer enough. Now user experience and ease of use are also critical for success.”

Despite all that, the survey found that 40% of companies surveyed “have no process in place for functional usability testing.” Given that, it should be no surprise that nearly half of the executives surveyed said that at least 50% of their software projects, including mobile apps, fail — they are either over budget, late, don’t meet expectations, or need to be reworked.

Solving Mobile App Development Woes

What can enterprises do to make sure their mobile app development efforts succeed? Start with aligning business needs with the development process, the survey recommends. Business stakeholders must be involved from the beginning, and clearly explain their needs and requirements. Once that’s done, they should be involved early on in testing the application to make sure it does what they need it to do.

Next, CIOs must “prioritize the project timeline and determine which applications are business critical.” Not uncommonly, CIOs are in charge of hundreds of projects. They have a hard time vetting bad ideas early on and prioritizing the most important projects. The answer: better communication with business teams. If business stakeholders more clearly communicate what’s most important to them, CIOs can more easily make the right decisions.

The survey has many more recommendations, advice, and findings. To read it, click here.

mobile app

Published at DZone with permission of Amy Groden-Morrison, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • DevOps for Developers: Continuous Integration, GitHub Actions, and Sonar Cloud
  • Custom Validators in Quarkus
  • How To Choose the Right Streaming Database
  • HTTP vs Messaging for Microservices Communications

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: