This article is a memo that will remind you about the things you need to design before sending your app to AppStore/GooglePlay. The list is divided into a few important sections:
Splash screen is the screen that shows up when users launch a mobile app. Since the splash screen is the first screen the users see, it creates the first impression for users even before they start using your app.
The average person is registered to 90 online services that require passwords. With so many accounts in use, very few people remember their passwords. According to statistics, 21 of users forget passwords after two weeks, and 25 percent forget one password at least once a day. If your app requires log in, then you should provide an option to reset the password.
Onboarding is a term used by UX designers to describe a process of getting users "up and running" with an app. Successful onboarding increases the likelihood that a first-time user becomes a full-time user after adopting a product.
Many mobile apps ask to confirm email/phone number. Data confirmation screen usually comes after a user provides the required details and tells them to go and confirm their email address/phone number.
For data confirmation screens, it's vital to provide:
Content is what provides value for most apps. It's the primary reason why people are using them - for the content. Thus, it's critical to consider how to design places in the user journey where a user might not have content yet. Such places are known as empty states, and empty states shouldn't be…well, empty. An empty state is a natural point to inject some onboarding to continue guiding users along. Instead of leaving it blank, you should use it efficiently - to educate and guide.
A majority of users (~95% according to Jared M. Spool) do not change default settings. It means that a majority of users will have a default avatar that you will select for them.
When users open a new app, the last thing they want to see is multiple popups in a row asking for permissions:
Such permission requests have a very negative impact on user experience and usually leads to the app abandonment. That's why it's much better to ask permissions in the content of user interactions.
Buttons and other interactive elements often have multiple states. It's vital to consider states like Default/Pressed/Disabled for every interactive element you have in your app.
It's possible to make your UI more visually consistent by using icons with the same style.
We all know that the best error message is the one that never shows up. It is always better to prevent errors from happening in the first place by guiding users in the right direction ahead of time. But, when errors do arise, well-designed error handling not only helps teach users how to use the app as you intended but also prevents users from feeling ignorant.
Here are a few error cases that you should design for:
While an instant response from an app is the best, there are times when your app won't be able to comply with the guidelines for speed. A bad internet connection could cause a slow response, or operation itself can take a long time. For such cases, to minimize user tension, you must reassure users that the app is working on their request. When an app fails to notify users that it's taking time to complete an action, users often think the app didn't receive the request, and they try again. Plenty of extra taps have resulted due to a lack of feedback.
A wait-animation progress indicator is the most common form of providing a system status for users when something is happening or loading.
Success states are screens that we show to users when they complete tasks. Designers should consider the following types of success states:
Designers should always strive to minimize the interaction cost by removing unnecessary actions. Autocomplete simplifies user input by reducing the number of taps the user has to make in order to fill out the query.
We all make mistakes, but when it comes to user experience, it is vital to provide an option that helps the user to recover important data.
Since many product teams have plans for global reach, it's vital to make localization/internationalization a natural part of the design process. The visual properties of elements (such as size) and UX copy should be selected with localization/internationalization in mind.
When users have a problem, their first natural reaction will be to search for a solution within the app. That's why it's a good idea to provide a link to the Help/FAQ section in app.
Accessibility enables people with all abilities to perceive, understand, and interact with your product. Here is an excellent summary from Lillian Xiao on what designers need to know about mobile accessibility.
Did you know that lousy-designed notifications are the #1 reason why users uninstall the app?
However, it's possible to turn this anti-UX pattern into something meaningful and useful both for a business and for a user. To achieve good results with in-app notifications, designers need a publishing strategy that best fits mobile medium.
It's always great to provide users a freedom of choice. In the context of mobile notifications, it means providing an opportunity to choose what notifications they want to receive.
Allow users not only to upload the avatar but also modify it according to their needs right in your app.
Allow users to edit their personal information right in the mobile app. Design screens to preview Shipping/Billing info and make this info editable.
If your app requires sign in, you should always allow users to sign out.
Add Terms of Service to your app to avoid getting sued.
Allow users to see what data they share with a company and allow them to customize the settings.
By providing a quick route for sharing feedback about your product, not only you collect valuable insights about your product from real users but also make them believe their feedback is valuable for you.
Mobile displays have limited screen estate. In order to save screen space, designers often want to optimize the displayed information and hide anything that is not valuable for the user. That's why many feed screens have two states - default state (the screen that users see when they enter the feed) and on-scroll state (when the user swipes up to see more content).
You need to decide what will be a default order for the search results. For example, if you design search results page for an e-commerce app, you need to decide whether the output should be sorted by best match/price/delivery time.
Allow users to share or bookmark a particular item from search results.
What screen will our users see when they search for a particular item, but the app does not have any matching results. "No results" screen should not act as a dead end. That's why instead of showing a blank page with a quick note "No results," we should design a screen that guides users and shows what they can do next.
You need to design a memorable icon for your app, something that will reflect the nature of your app and create interest for potential users.