{"id":1173,"date":"2018-10-01T13:30:14","date_gmt":"2018-10-01T13:30:14","guid":{"rendered":"https:\/\/azoora.com\/blog\/?p=1173"},"modified":"2019-04-24T11:50:29","modified_gmt":"2019-04-24T11:50:29","slug":"mobile-app-design-best-practices-mistakes","status":"publish","type":"post","link":"https:\/\/azoora.com\/blog\/information\/mobile-app-design-best-practices-mistakes\/","title":{"rendered":"Mobile App Design: Best Practices & Mistakes"},"content":{"rendered":"\n

In 2017, over 91 billion apps<\/a> were downloaded from the iOS App Store and Google Play (which doesn\u2019t include all of the third-party app stores and app stores for other platforms). That\u2019s a lot of apps\u2014roughly 13 per person\u2014on the entire planet. With so many apps being downloaded, it\u2019s no wonder that the average app has a churn rate of 57%<\/a> in the first month (users who don\u2019t open the app more than once during the first 30 days after downloading it) and a whopping 71% after 90 days.<\/p>\n\n\n\n

If any part of an app is undesirable, or slow to get the hang of, users will opt to install a new one rather than stick it out with the imperfect product. Nothing is wasted for the consumer when disposing of an app, other than possibly a few dollars (and they know they can download the app again at any time). The only loss is the time and effort of the designers and developers.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

So, why is it that so many apps fail? Is this a predictable phenomenon that app designers and developers should accept? For clients, is this success rate acceptable? What does it take to prevent your apps from being deleted without a second thought?<\/p>\n\n\n\n

The most common mistakes span from failing to maintain consistency throughout the lifespan of an app to difficulty attracting users in the first place. It\u2019s challenging to design an app with intuitive simplicity without it becoming repetitive and boring. An app has to offer pleasing design and UX details without losing sight of a greater purpose.<\/p>\n\n\n\n

Most apps live and die in the first few days, so following some basic mobile app design best practices and avoiding the most common mistakes will help designers create apps that live past that 90-day mark.<\/p>\n\n\n\n

Common Mistake #1: A Poor First Impression<\/h3>\n\n\n\n

Often, the first use or first day with an app is the most critical period to hook a potential user. The first impression is so critical that it could be an umbrella point for all of the other mobile design best practices. If anything goes wrong, or appears confusing or boring, potential users are quickly disinterested.<\/p>\n\n\n\n

The proper balance for first impressions is tricky, though. In some cases, a lengthy onboarding process to discover necessary features can bore users. Yet without proper onboarding<\/a>, some apps will just confuse users if they\u2019re not instantly intuitive. Creating an app that is immediately intuitive while also introducing users to the most exciting, engaging features quickly is a delicate balancing act.<\/p>\n\n\n\n

Although it can be a good way to get someone quickly oriented, drawn-out onboarding can also stand in the way of users doing what they want to do with the app. Often, these tutorials are too long and are swiped through blindly.<\/p>\n\n\n\n

Keep in mind that when users first use an app, they don\u2019t necessarily have any waypoints for how the app should function or what it can do. Proper beta testing process allows designers to learn how others perceive an app from the beginning. What seems obvious to the design team may not be for newcomers.<\/p>\n\n\n\n

\"\"

Mobile onboarding design (by Johan Adam Horn<\/a>)
<\/figcaption><\/figure>\n\n\n\n

Common Mistake #2: Designing an App Without Purpose<\/h3>\n\n\n\n

Avoid entering the design process without clear intentions. Apps are too often designed and developed in order to follow trends rather than to solve a problem, fill a niche, or offer a distinct service.<\/p>\n\n\n\n

For the designer and their team, the app\u2019s purpose will affect every step of a project. It guides every decision, from the branding or marketing of an app to the wireframe format to the button aesthetic. If the purpose is clear, each piece of the app will communicate and function as a coherent whole.<\/p>\n\n\n\n

Conveying this vision to potential users means that they will understand the value an app brings to their life. The vision needs to be clearly communicated from the user\u2019s first impression. How quickly can the vision for the app be conveyed to users? How will it improve a person\u2019s life or provide some sort of enjoyment or comfort? As long as an app\u2019s usefulness is conveyed immediately to users, it\u2019s likely to be part of the 21% of apps that make it past the first 90 days.<\/p>\n\n\n\n

When entering an existing market, there are apps designed for that space designers can study as a baseline. They can improve upon what is already out there or provide a unique alternative in order to stand out. They shouldn\u2019t thoughtlessly imitate.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Common Mistake #3: Failing to Optimize User Flow<\/h3>\n\n\n\n

Designers should be careful not to skip over thoughtful planning of an app\u2019s UX architecture before jumping into design work. Even before getting to a wireframing stage, the user flow and structure of an app should be mapped out. Designers are often too excited to produce aesthetics and details. This results in a culture of designers who generally under-appreciate UX and the necessary logic or navigation within an app.<\/p>\n\n\n\n

Slow down. Sketch out the flow of the app first before worrying too much about the finer details. Apps often fail from a lack of flow and organization, rather than imperfect details. Once the design process takes off, always keep the big picture in mind. The details and aesthetic should then clearly evoke and reinforce the greater concept.<\/p>\n\n\n\n

\"\"

A well-thought-out user flow diagram (by Michael Pons<\/a>)
<\/figcaption><\/figure>\n\n\n\n

Common Mistake #4: Disregarding App Development Budget<\/h3>\n\n\n\n

As soon as the basic features and functions of an app are sketched, it\u2019s a good time to talk about the budget with the development team. This prevents spending a ton of time designing features and UX patterns that end up needing to be cut when the development team doesn\u2019t have the resources to implement them.<\/p>\n\n\n\n

Learning the average costs of constructing particular concepts is a valuable addition to a designer\u2019s toolkit, as it makes it easier to adapt design thinking to economic constraints. Budgets should be useful design constraints to work within, rather than viewed as frustrations.<\/p>\n\n\n\n

Common Mistake #5: Cramming in Design Features<\/h3>\n\n\n\n

Hopefully, rigorous wireframing and prototyping will make the distinction between necessary and excessive functions clear. Each individual mobile platform is already the ultimate swiss army knife, so your app doesn\u2019t need to be. Not only will cramming an app with features lead to a disorienting user experience, but an overloaded app will also be difficult to market.<\/p>\n\n\n\n

\"\"

Many failed apps try to cram too many features in from launch.
<\/figcaption><\/figure>\n\n\n\n

If the app can\u2019t be explained in a concise way, it\u2019s likely trying to do too much. Paring down features is always hard, but it\u2019s necessary. The best strategy might be to gain users in the beginning with just one or two features before testing new additions in later releases to see what resonates with users. This way, the additional features are less likely to interfere with the crucial first few days of an app\u2019s life.<\/p>\n\n\n\n

Common Mistake #6: Dismissing App Context<\/h3>\n\n\n\n

Although purpose and end goals are important, they become irrelevant if not directed within the proper context. The UI for a given app may seem obvious to the design team, but first-time users and users from different demographics may not find it as intuitive. For example, millennial users of an app might find certain functions intuitive, while retirees might find those same things confusing (or vice versa).<\/p>\n\n\n\n

Consider the immediate context or situation in which the app is intended to be used. For example, Uber\u2019s <\/a>interface excels at being used very quickly. This is perfect because when a user is out with friends and needs to book a ride, they barely have to interrupt their conversation in the process. Uber hides a lot of support content deep within the app that only appears when the scenario calls for it.<\/p>\n\n\n\n

Is your app meant to be accessed quickly and for a short period of time? Or, is this an app with lots of content that allows users to stay a while? How will the design convey this type of use? Consider these points carefully when mapping out your app\u2019s UX flow.<\/p>\n\n\n\n

\"\"

Good mobile design should consider the context in which it is used.
<\/figcaption><\/figure>\n\n\n\n

Common Mistake #7: Abusing Notifications<\/h3>\n\n\n\n

Push notifications<\/a> are a finicky part of app design best practices. Too many, and users will turn them off entirely, risking the app being forgotten about. Too few, and the same fate occurs.<\/p>\n\n\n\n

But it\u2019s not just the frequency of notifications that can turn users on or off. It\u2019s also the content. Useful notifications, such as those notifying users of a new message or reminding them to make a daily check-in, are seen as helpful and necessary. Apps that send seemingly random updates or notifications about news that doesn\u2019t directly affect the user are more likely to see their notifications turned off completely.<\/p>\n\n\n\n

Every notification is a microinteraction that can either enhance the user experience and reinforce the overall usefulness of the app or risk alienating users and, in extreme cases, prompting them to delete the app all together.<\/p>\n\n\n\n

\"\"

Push notifications are a delicate balancing act in good mobile design (by Jona Nalder<\/a>).
<\/figcaption><\/figure>\n\n\n\n

Common Mistake #8: Overcomplicating App Design<\/h3>\n\n\n\n

The famous architect Mies Van der Rohe once said, \u201cIt\u2019s better to be good than to be unique.\u201d It\u2019s vital that the design meet the specs in the brief before designers start breaking the box or adding other flourishes.<\/p>\n\n\n\n

Design elements added to make a composition more visually appealing still need to add value to the user experience. Continue to ask throughout the design process, how much can I remove? Design reductively instead of additively.<\/p>\n\n\n\n

Over-complexity is often a result of unnecessarily breaking conventions. Will the app really benefit from reworking the standard symbols and interfaces within mobile visual and tactile language? Standard icons have proven themselves to be universally intuitive. Thus, they are often the quickest way to provide visual cues without cluttering a screen.<\/p>\n\n\n\n

Don\u2019t let design flourishes get in the way of the actual content or function of the app. Often, apps are not given enough white space. While it\u2019s vital to good design in general, it\u2019s especially important for mobile designs, as a cluttered interface isn\u2019t particularly touch-friendly.<\/p>\n\n\n\n

\"\"

The app design process can be reductive, rather than additive.
<\/figcaption><\/figure>\n\n\n\n

Common Mistake #9: Design Inconsistencies<\/h3>\n\n\n\n

If a design is going to introduce new standards, they have to at least be consistent across the app. Each new function or piece of content doesn\u2019t necessarily have to be an opportunity to introduce a new design concept.<\/p>\n\n\n\n

Is the text uniformly formatted? Do UI elements behave in predictable, yet pleasing ways throughout the app? Design consistency must find the balance between existing common visual language and avoiding being aesthetically stagnant. The balance between intuitive consistency and boredom is a fine line.<\/p>\n\n\n\n

Common Mistake #10: Under-utilizing App Beta Testing<\/h3>\n\n\n\n

All designers should analyze the use of their apps with some sort of feedback loop in order to learn what is and isn\u2019t working. A common mistake in testing is for a team to do their beta testing in-house. It\u2019s imperative to bring in fresh eyes in order to really dig into the drafts of the app.<\/p>\n\n\n\n

Send out an ad for beta testers and work with a select audience before going public, or use a testing service like UserZoom<\/a>. This can be a great way to iron out details, edit down features, and find what\u2019s missing. Beta testing can be time consuming, but it\u2019s definitely a better alternative to developing an app that flops.<\/p>\n\n\n\n

\"\"

Designers should pay special attention to mobile user testing as potential users are fickle (source: Fake Crow<\/a>).
<\/figcaption><\/figure>\n\n\n\n

It\u2019s important for design teams to recognize just how competitive the mobile app market is and to do whatever possible to differentiate their offering from the hundreds or thousands of other apps occupying the same space. To do this, they need to have a coherent vision of what the mobile app is hoping to achieve. Following mobile app design best practices and using an iterative design process that incorporates user feedback into the entire process is one of the best ways to do this, and will create an app that stands out.
<\/p>\n","protected":false},"excerpt":{"rendered":"

In 2017, over 91 billion apps were downloaded from the iOS App Store and Google Play (which doesn\u2019t include all of the third-party app stores and app stores for other platforms). That\u2019s a lot of apps\u2014roughly 13 per person\u2014on the entire planet. With so many apps being downloaded, it\u2019s no wonder that the average app has a churn […]<\/p>\n","protected":false},"author":2,"featured_media":1253,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[102,85,77],"tags":[103,86,112],"jetpack_featured_media_url":"https:\/\/azoora.com\/blog\/wp-content\/uploads\/2018\/11\/toptal-blog-image-1526473446814-22370277d9306ec963e85d28f3306ecf.png","jetpack_publicize_connections":[],"jetpack_shortlink":"https:\/\/wp.me\/p7FQPL-iV","jetpack-related-posts":[],"jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/posts\/1173"}],"collection":[{"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/comments?post=1173"}],"version-history":[{"count":2,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/posts\/1173\/revisions"}],"predecessor-version":[{"id":2259,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/posts\/1173\/revisions\/2259"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/media\/1253"}],"wp:attachment":[{"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/media?parent=1173"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/categories?post=1173"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/azoora.com\/blog\/wp-json\/wp\/v2\/tags?post=1173"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}