{"id":9994,"date":"2016-03-01T10:54:13","date_gmt":"2016-03-01T16:54:13","guid":{"rendered":"http:\/\/www.mrc-productivity.com\/blog\/?p=9994"},"modified":"2022-11-22T16:22:25","modified_gmt":"2022-11-22T22:22:25","slug":"how-to-build-enterprise-mobile-apps-that-users-hate","status":"publish","type":"post","link":"https:\/\/www.mrc-productivity.com\/blog\/2016\/03\/how-to-build-enterprise-mobile-apps-that-users-hate\/","title":{"rendered":"How to build enterprise mobile apps that users hate"},"content":{"rendered":"

\"Education\"Summary: Many companies rush into mobile apps, completely unaware of the risks and challenges that come with the territory. The result: They deliver an app that nobody wants to use–completely wasting the time and money invested in the development process. In this article, we identify some of the biggest mistakes businesses make with mobile app development, and explain why they must be avoided.<\/em><\/span>
\n<\/a><\/p>\n

Over the past year, the growth of enterprise mobile apps has skyrocketed. Identified by one survey<\/span><\/a> as the top CIO priority for 2016, IT leaders have recognized the importance of mobilizing their enterprise applications.<\/p>\n

But, there\u2019s just one slight problem. Mobile app development is uncharted territory for most IT departments. As they race to create mobile apps for their customers\/employees, many make critical mistakes along the way. <\/p>\n

The result<\/strong>: They deliver apps that their users hate. In fact, one study found that nearly 80% of enterprise mobile apps are abandoned<\/span><\/a> after their first use. <\/p>\n

Why does this happen? What mistakes lead to this app abandonment?<\/p>\n

Today, let\u2019s answer those questions. We\u2019ll identify common mobile app mistakes and explain why they must be avoided. Here are 7 critical mobile app development missteps that will result in an app that your users hate:<\/p>\n

1. Ignore user context<\/h3>\n
\"photo
photo credit: geralt<\/a> via pixabay<\/a> cc<\/a><\/figcaption><\/figure>\n

Before you consider a mobile business application, you must ask a couple of questions: Why do our customers\/employees need a mobile app? How will this help them solve a problem they currently face?<\/p>\n

Ignore those questions, and nothing else matters. Nobody will use your app.<\/p>\n

Yet, this is an issue we see regularly. Businesses approach mobile apps from their own perspective (not the user\u2019s needs). They build mobile apps just to keep up. They deliver apps that their customers\/employees don\u2019t need or want. As explained below, ignoring the user\u2019s needs is the surest way to guarantee that nobody uses your app.<\/p>\n

\n\u201cThe biggest mistake is not understanding the context,\u201d says Mobile Expert Will Pate<\/span>. \u201cWhat job is the user hiring the app to do? Are helping them accomplish that job in a way that is demonstrably better than the current alternatives? If you’re not solving a user’s problem in a clear and immediate way, nothing else you do can save your app because it’s irrelevant to the user.\u201d\n<\/p><\/blockquote>\n

2. Focus only on function<\/h3>\n

Now, your mobile app may meet your user\u2019s needs…and still fail. It may deliver every feature they requested. Yet, the users still hate it.<\/p>\n

Why?<\/p>\n

Delivering a truly useful mobile app goes beyond features. It\u2019s all about the experience. Is the app confusing? Does it try to do too much? Does it require training? If you answer \u201cYes\u201d to any of those questions, your app will most likely fail. A successful app focuses on both function and experience, and involves the users along the way.<\/p>\n

\n\u201cI worry about code and functionality – but the truth is that the best way to make an awful app is to focus only on quickly delivering “correct” functions, then shipping,\u201d says David Ashe, Developer & Organizer, NYC Bootcampers Anonymous<\/span><\/a>. \u201cEither a User Experience designer or developers familiar with UX must do initial AS WELL AS mid-project UX testing or the app will be a Palm Pilot while someone else delivers an iphone. Merely guessing from the beginning what will make the app useful is nothing compared to several rounds of live user testing.\u201d\n<\/p><\/blockquote>\n

3. Try to fit every feature into your app<\/h3>\n
\"photo
photo credit: Walter Benson<\/a> via photopin<\/a> cc<\/a><\/figcaption><\/figure>\n

Yet another common mistake found in many business mobile apps: They try to do too much. The developers try to cram every feature into the app. After all, more features is good…right?<\/p>\n

Quite the opposite. With mobile apps, less is more.<\/p>\n

Look around at some of the most popular mobile apps. They succeed because they eliminate complexity. They focus on one or two primary goals, and eliminate the rest. <\/p>\n

If your enterprise mobile app is going to succeed, you must first identify its goal. What one or two tasks will it help the user accomplish? How easily can they accomplish those tasks?<\/p>\n

\n\u201cThe whole philosophy of making enterprise processes on your phone is to simplify, but the biggest trap I see enterprise apps fall into is information overload,\u201d says Sloane Berry, UX designer at BPM Technologies<\/span><\/a>. \u201cWhen you have long pages that you have to scroll through or if you have to click through several pages to get your information it creates a bad user experience. You want to be able to view your most important items on a dashboard at a glance, and then have the option to dig deeper. The key is keeping apps to as few pages as possible, without being sensory overload.\u201d<\/p>\n

\u201cIt\u2019s important not to have the app do too much. The industry is moving toward more and more simple processes. The most successful consumer apps offer one thing and only require you to press one button. While enterprise apps may need to be more complex, that complexity shouldn\u2019t trickle down to the user. The whole mobile app industry is moving toward one-click gratification and it\u2019s become the most desirable way for people to interact with technology.\u201d\n<\/p><\/blockquote>\n

4. Ignore connectivity <\/h3>\n

What is the biggest advantage of building mobile web apps for your business? You have your data and applications with you wherever you go! You can reach your customers anywhere!<\/p>\n

But, what happens if you lose your data connection? After all, what if your salespeople venture into a rural area? What if your field technicians work in a location with spotty coverage? Are your mobile web apps worthless without a data connection? If so, you\u2019ll only frustrate your users.<\/p>\n

While improving, mobile networks still don\u2019t offer 100% coverage everywhere. Unfortunately, many businesses don\u2019t factor this into their development–resulting in an app that frustrates users.<\/p>\n

\n\u201cMany applications become useless when out of mobile data coverage,\u201d explains Nic Grange, CTO of Retriever Communications<\/span><\/a>. \u201cThis can result in losing data entered and making users having to re-enter it which users obviously hate.\u201d\n<\/p><\/blockquote>\n

Quick note<\/strong>: Many think that the need for offline capabilities eliminates mobile web apps. This is a myth. HTML5 brings offline capabilities to web (and mobile web) apps, meaning your mobile web apps can function without a data connection. <\/p>\n

5. Ignore perceived speed<\/h3>\n
\"photo
photo credit: geralt<\/a> via pixabay<\/a> cc<\/a><\/figcaption><\/figure>\n

According to recent research<\/span><\/a>, speed is even more important for mobile apps than it is for typical websites. Users will not tolerate mobile apps that are slow to open or operate.<\/p>\n

But, what does application “speed” actually mean? Traditionally, it refers to response time–how quickly the application responds to user requests. But, research<\/span> has found that lowering the response time isn’t the only way to improve application speed. In fact, “perceived performance” may actually be more important than actual performance.<\/p>\n

\n\u201cWhile application speed is critical to mobile app usability, we\u2019ve found that it goes a step beyond that,\u201d says Brian Duffey, a Consultant at mrc<\/span><\/a>. \u201cIt\u2019s not so much how fast the application is, as much as how fast the application feels to the user. It\u2019s the perceived speed that makes the difference. This can be accomplished by adding touch states to your buttons or using unique loading animations, among other things. In making the application feel fast and responsive, the user believes it is faster.\u201d\n<\/p><\/blockquote>\n

6. Deliver too many notifications<\/h3>\n

Native apps let you deliver push notifications to the user\u2019s device. These notifications alert the user to important news or information. <\/p>\n

The problem is, many developers abuse this privilege. They send push notifications for minor events. Why is this such a problem? <\/p>\n

First, it annoys the user. They\u2019re already receiving notifications from their other apps. What happens when they start seeing unnecessary notifications from yours? They\u2019ll get frustrated and may even delete your app.<\/p>\n

Second, you train the user to ignore your notifications. If most of them aren\u2019t important, they\u2019ll skip over every one…negating the effectiveness of push notifications altogether.<\/p>\n

\n\u201cOne way I’ve seen enterprise apps fail is because app makers don’t think about the frequency of the communication,\u201d says Julie Ginches, CMO at Kahuna<\/span><\/a>. \u201cThere are some mission-critical apps where push notifications can and should come through the second they’re available (i.e. for a support app or a systems uptime app) but inundating your workers with irrelevant messages is an easy way to get people to ignore or delete the app.\u201d\n<\/p><\/blockquote>\n

7. Apply excessive security controls<\/h3>\n
\"photo
photo credit: stevepb<\/a> via pixabay<\/a> cc<\/a><\/figcaption><\/figure>\n

Now, don\u2019t get me wrong. I\u2019m not telling you to create vulnerable applications. However, you must understand the differences between mobile apps and desktop apps, and adjust accordingly.<\/p>\n

For instance, what happens if you force users to log out every couple of hours? On a desktop, it\u2019s not a big deal. But, on a mobile device, that\u2019s a major inconvenience. While proper security is essential in mobile app development, you must implement it in such a way that it doesn’t cripple the app’s experience.<\/p>\n

\n\u201cExcess security on mobile devices can render them almost unusable,\u201d says Grange. \u201cUsers will either not use the device or they will find ways around it like sticky tapping the password to the device. The security controls need to consider the user experience and reflect the often limited access that users have on a mobile device.\u201d\n<\/p><\/blockquote>\n

Summary<\/h3>\n

While this list could certainly go on, the points listed above are just a few of the common mistakes businesses make with their mobile app development. What do you think? Would you add anything to the list? If so, please feel free to share in the comments.<\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Many companies rush into mobile apps, completely unaware of the risks and challenges that come with the territory. The result: They deliver an app that nobody wants to use–completely wasting the time and money invested in the development process. In this article, we identify some of the biggest mistakes businesses make with mobile app …<\/p>\n

How to build enterprise mobile apps that users hate<\/span> Read More »<\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"default","ast-global-header-display":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","slim_seo":{"title":"How to build enterprise mobile apps that users hate - mrc's Cup of Joe Blog","description":"Summary: Many companies rush into mobile apps, completely unaware of the risks and challenges that come with the territory. The result: They deliver an app that"},"footnotes":""},"categories":[8],"tags":[34,35],"class_list":["post-9994","post","type-post","status-publish","format-standard","hentry","category-education","tag-mobile","tag-mobile-apps"],"_links":{"self":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/9994","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/comments?post=9994"}],"version-history":[{"count":15,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/9994\/revisions"}],"predecessor-version":[{"id":14238,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/9994\/revisions\/14238"}],"wp:attachment":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/media?parent=9994"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/categories?post=9994"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/tags?post=9994"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}