{"id":9614,"date":"2015-10-30T23:28:58","date_gmt":"2015-10-30T23:28:58","guid":{"rendered":"http:\/\/proxystudio.uxpin.com\/?p=9614"},"modified":"2026-05-08T01:07:24","modified_gmt":"2026-05-08T08:07:24","slug":"dont-forget-to-design-these-mobile-app-design-elements","status":"publish","type":"post","link":"https:\/\/www.uxpin.com\/studio\/blog\/dont-forget-to-design-these-mobile-app-design-elements\/","title":{"rendered":"Don\u2019t Forget to Create These Mobile App Design Elements"},"content":{"rendered":"

Designing mobile apps is a long and difficult process that spans the moment an idea arises to when we finally upload the finished application.<\/p>\n

During that journey, we go through multiple defined stages, like wireframing<\/a>, visual design<\/a>, and building animated prototypes. In the midst of all the transition, it’s easy to skimp over design elements that feel like UX “nice-to-haves”.<\/p>\n

In essence, I’m talking about elements such as empty screens, edge cases, placeholders (like loading screens), and micro-interactions. I’ll explain why these subtleties are just as important as the more obvious<\/i> components of the UI, and how they help determine the success or failure of our app.<\/p>\n

Empty screens or blank slates<\/i><\/h2>\n

When we are wrapped up in the design process, we normally design for a populated interface where everything in the layout looks well arranged.<\/p>\n

In those cases, we must design the ideal amount of information in a packed screen: for example, a list of favorite items or a contact list with items already in there.<\/p>\n

But how should we design our screen when the content is pending user action? Even if it’s meant to be just a temporary stage, we must respect its communication value for users.<\/p>\n

\"image06\"<\/p>\n

The purpose of a blank slate is more than a just decoration. Besides informing the user about what content to expect on the page, empty states also act as a type of onboarding. They tell users exactly actions are required so that content can appear and the app will function as promised.<\/p>\n

When you really think about it, such simple pages actually carry quite a large responsibility.<\/p>\n

Let’s think about a real-life example to put things in perspective. When you first walk into a hotel, the receptionist usually explains where your room and other facilities are located, where and when to eat breakfast, and how and when to check out. Before you can enjoy your stay at the hotel, you experience an “empty state” in which context is required to orient yourself and proceed onwards.<\/p>\n

Just like you want the guest in their room enjoying their stay as quickly as possible, you want your users to do something so that the screen won’ empty<\/i> as soon as possible. Here’s a few tips to keep in mind:<\/p>\n