A mobile user interface (mobile UI) is the graphical and usually touch-sensitive display on a mobile device, such as a smartphone or tablet, that allows the user to interact with the device’s apps, features, content and functions. Mobile user interface (UI) design requirements are significantly different from those for desktop computers. The smaller screen size and touch screen controls create special considerations in UI design to ensure usability, readability and consistency. In a mobile interface, symbols may be used more extensively and controls may be automatically hidden until accessed. The symbols themselves must also be smaller and there is not enough room for text labels on everything, which can cause confusion. Users have to be able to understand a command icon and its meaning whether through legible text or comprehensible graphical representation. Basic guidelines for mobile interface design are consistent across modern mobile operating systems. Mobile UI design best practices include the following: The layout of the information, commands, and content in an app should echo those of the operating system in placement, composition and colors. While apps may diverge to some degree in style, consistency on most of these points allows users to intuit or at least quickly learn how use an interface. Click points must be usable for touch-based selection with a finger. This means a click point can't be too small or narrow in any direction, to avoid unwanted selection of nearby items, sometimes referred to as fat fingering. Maximize the content window size. On small screens, the UI should not unnecessarily dominate screen size. It’s important to recognize that the object of a UI is to facilitate use of content and apps, not just use of the interface. The number of controls or commands displayed at any given time should be appropriate to avoid overwhelming the user or making viewing/interacting with content confusing.
Stay organized with collections Save and categorize content based on your preferences. Last updated: May 17, 2021 A useful way to evaluate app excellence is to walk through the workflows in your app and evaluate the smoothness and safety of the app experience. This checklist defines a set of core quality criteria and associated tests to help you assess the quality of your app. Some of these criteria might be easy to miss, and the tests help you remember to include them in your test plans. The checklist highlights the minimum quality that all apps should meet. Your testing will likely go well beyond what's described here. Each item in the quality checklist has a unique ID which you might find helpful to use when you communicate with your team. You can also view the previous version of these guidelines. Your app should provide standard Android visual design and interaction patterns where appropriate, for a consistent and intuitive user experience. We recommend using Material Design Components for creating a user interface in place of Android platform components where possible. This enables the modern Android look and feel, and it helps provide UI consistency across Android versions.
Your app should implement the expected functional behavior.
Your app should provide the performance, stability, compatibility, and responsiveness expected by users.
Your app should handle user data and personal information safely, with the appropriate level of permission. In addition to this checklist, applications published on the Google Play Store must also follow the User Data policies to protect users' privacy.
Be sure that your apps can be published on Google Play.
For the purpose of setting up a test environment for this checklist, we recommend the following:
For more comprehensive guidance on testing including unit testing, integration testing and UI testing, check out the Android testing fundamentals. These test procedures help you discover various types of quality issues in your app. You can combine the tests or integrate groups of tests together in your own test plans. See the sections above for references that associate criteria with these test procedures.
Testing with StrictModeFor performance testing, we recommend enabling StrictMode in your app and using it to catch operations that could affect performance, network accesses, file reads/writes, and so on. Look for potentially problematic operations both on the main thread and on other threads. You can set up a per-thread monitoring policy using StrictMode.ThreadPolicy.Builder and enable all supported monitoring in the ThreadPolicy using detectAll(). Make sure to enable visual notification of policy violations for the ThreadPolicy using penaltyFlashScreen(). |