The five reasons why enterprise mobile apps fail


50% of enterprise mobile apps will need to be completely rewritten or replaced in two years. With the odds of success being no better than a coin-toss, it’s imperative that enterprises are taking the right steps to mobilise their business applications. The process is complex, error-laden, and resource-rich.  Having spoken to hundreds of companies and hearing their horror stories, here are the 5 reasons why enterprise mobile apps fail.

1) Building mobile apps like enterprise web apps

Enterprise applications work only one way - after logging in, you have to navigate through several pages to get to the relevant screen and your desired task. Mobile apps work completely different - they are built with a specific task in mind and enable you to complete it in less than a minute with minimal navigation. They’re simple, bite-sized, personalised, and contextual. With today’s mobile-mindset, if you plan on building mobile apps the same way monolithic enterprise apps are built; you’re going to fail.

2) API Access = risk

Gaining access via APIs to your enterprise applications is one of the toughest parts of the mobile app creation journey and could take as much as 12-24 months.  Anytime you deal with business logic, validations, access permissions, you’re adding risk and multiplying the layers of error-laden complexities. The more you can leverage a solution that doesn’t depend on APIs and automatically inherits role-based access and business logic, the more secure the solution will be.

3)  You’re waiting for developers…and still waiting

If your mobile journey is reliant on developers, be prepared to wait. According to Forrester Research, coding an enterprise mobile app takes 6-9 months and approximately $250K to develop. To make things tougher, finding mobile developer talent is very competitive – as mobile app developers have their pick of the litter and mobilising your enterprise application isn’t nearly as sexy as the next consumer mobile app.

4) You build it and no one comes

There’s a very high probability that once you spend all the time and money to build an enterprise app that you find no one is using it.  SAP reports that 78% of enterprise mobile apps are abandoned after the first use. Mobile adoption drastically depends on your ability to measure behaviours in your app quantitatively, gather feedback from your users and iterate quickly. According to a study from BI Intelligence, the more frequently an app is updated, the higher the user ratings. We’ve seen similar trends with our customer base, with the average app undergoing 15 iterations, each taking only about a day to do.

5) One down and how many more to go?

If you’re one of the few mobile teams who’ve launched a successfully adopted mobile app, you’re quite familiar with the cost and time it took. The average enterprise has more than 700 business applications.  If you were to mobilize even 10% of them, at six months of development time each, it would take 35 years to complete. If you’re reliant on an approach that requires APIs for access, developers to code, scalability is a serious problem.

Whether you’re on your first enterprise mobile app or your 100th, it’s clear that mobility is the road to productivity and profitability. In order to be successful, apps need to be delivered quickly and be easy to use. At Capriza, we believe the best way to do this is with user-centric design and an approach that leverages zero APIs, zero upgrades, and zero coding. in hearing industry leaders discuss subjects like this and sharing their use-cases? Attend the co-located IoT Tech Expo, Blockchain Expo, AI & Big Data Expo and Cyber Security & Cloud Expo World Series with upcoming events in Silicon Valley, London and Amsterdam and explore the future of enterprise technology.

Related Stories

Leave a comment


This will only be used to quickly provide signup information and will not allow us to post to your account or appear on your timeline.