Mobile app designing or mobile web designing is a bit different thing than standalone web interface designing. Naturally, mobile UI has altogether different user cases, scenario, gestures than desktop or laptop application.
Mobile Users Demand Quick Interactions
For instance, if you are designing an email interface, the behavior of your desktop audience would be quite different than a mobile user. Your desktop or laptop users have enough time to look at the various UI elements in the screen for email. Whereas your mobile users may be in a hurry to check email without much spending on the UI and its elements. They want a quick opening of email details just reading its subject/title.
However, it is not always true that mobile users demand quick interactions with each UI. For instance, you have a traveling application on your mobile and allows you to book a ticket online or through app itself. It is natural that you are facing such kind of application first time or in very seldom cases. Therefore, you need to learn all steps involved in ticket booking through on-screen help or smart UI designing. Thus, this sort of mobile application dominating with instructional UI elements or texts that correctly guide you in engaging ways.
Designing According to Tasks
In above two examples, we have seen that the user interaction speeds are differing according to the tasks and their demands. In case of email, our users are familiar with UI so learning is not necessary there. Whereas in case of ticket booking app, learning is mandatory for most of the users because traveling app usage is infrequent and seldom.
Designing for Momentum
In both cases of mobile app designing, we have mobile devices in use and user is in hurry whether to check the email or booking a ticket before train or plane take off. However, we canât offer same speed for app interactions for ticket booking users that we are offering our email surfers.
Reasons are obvious as email users are frequent users of those UIs so they are familiar with each UI component and its functionality. Whereas in case of ticket booking app, users are infrequent users and quite not familiar with the process of ticket booking and their UIs.
Therefore, mobile app designing team has to act altogether in different ways in both cases. In email case, they have to speed up the interactions by removing all obstacles or useless steps, UI elements, or delays. While in case of ticket booking, mobile app designers have challenges to let users understand the each step of ticket booking and make smart choices in their unique contexts. Besides these, mobile app designers have to place instructional UI elements or texts to guide users properly.
In psychological terms, mobile app designers have to add some frictions in case of ticket booking app. Therefore, the users or ticket bookers should have time to think on ensues of their actions on the mobile UI and its elements. This addition of friction is call momentum design and that is differing in both example cases.
There are many ways or techniques to add frictions in mobile app designing, but we donât have scope to discuss in this single post so we may take time in future posts. However, one thing we should remember that when we are going to designing for momentum and adding frictions, we should go judiciously and add only needed amount of frictions otherwise, users will leave the applications with bad experiences or with frustrations and never comeback.
This blog is listed under Digital Media & Games Community