1. Navigation 2.0


The debate over Top and Bottom is a long one, but we will be aiming at the end of the 21st. These two components of UX, widely accepted on iOS and Android, will define this transition: Bottom Sheet and Swipe Up Gestures.

Generally users are comfortable with the use of old fingers for any work done on mobile. Due to the large screen device and the tendency to use one hand, the bottom part of the screen is perfect for placing and holding important buttons.


  • Bottom sheet:

Designers generally prefer the bottom sheet for sub-floss instead of other elements such as overflow drop-down, hamburger side-drawer and pop-up dialog.

Bottom sheet is extremely flexible as it facilitates vertical scroll for additional content and horizontal scroll for simulator content. Previously no task could have been possible without the jumping screen. It is possible to design the end-to-end sub-floss evenly on the bottom sheet, with the primary context as anchor in the background.


  • Swipe up gestures:

Currently Swipe Up Gestures has replaced the Home button / Bottom tab bar for closing an app, returning it, and opening the app drawer.

There are two clear sections: Content (Top Area) and Navigation (Bottom Area) will standardize the floss in popular apps, and reduce cognitive load in increasing user confidence.

Recent updates to both Material and H-IG include instructions for bottom navigation.


2. Voice Interplay and Visual Interfaces:

Voice interfaces are another big and important aspect of human-computer interaction. Although the visual and voice interfaces remain fundamentally distinct, both will see acceptance on an equal scale in 2019.

At Visual UES we may or may not get the mic button.

If you want to talk while the app is being used, say it and the app will interpret it according to context and it will be transparent.

Suppose you are driving, it is possible to just receive a call saying “Pick it up” and read a notification that read “Read it for me”. What does that mean ”If you don’t want to scroll long scrolls on the small screen, say” Show me the cheapest option and the fastest option “or skip the entire flow and say” Find the cheapest option and book it using my Amex “. It is very easy to send text “chat uhhhhh” during chatting and share location as “share live location for 30 mins”.


3. Vernacular is not for content only:

When the next world is in the hands of billions of users, localization is not just content. Copy, icono/topography, colors, UI Interface metaphors, and UX flows and features.

For example, Vernacular users have an English UI on Facebook but juxtapose local copies of “What’s on your mind”.

PayTm provides a localized UI for each language and Sharechat hides a feature for adult languages.

Google Tez (now Google Pay) was built primarily for local users and has given prominence to digital trust building through the use of Explicit Messaging, Simple Flows and Minimal features.

In a recent user study of a Level 3 city in Tamil Nadu, our users prefer local metaphors like Namast, Garland, etc., rather than “liking” for something to appreciate. Imagine it from a user’s perspective. Unlike many, he is new to the Internet. His ideas are high for his (contextual) and his learning curve (for English) is limited. He can’t use a product until it’s ready for him.

In a recent user-level study, they used local metaphors like namaste, garland, etc. instead of “like” to honor something in three cities in Tamil Nadu. Think from a user’s point of view. Maybe he is not like the rest, he is new to the internet. Maybe his ideas are limited in terms of context and the learning curve (for English) is higher. And so he won’t be able to use it until a product is ready for him.

There are many examples of how apps increasingly integrate multiple languages ​​into products.


4. Design Systems:

  • Two important design systems:
  1. Content on apps and Android on Android and Human Interface Guidelines on iOS
  2. These systems provide guidelines for commonly used components, such as: headers, cards, bottom sheets, etc.

The code libraries of the components are also extremely accessible and useful to use. The default design systems actually ensure the performance and affinity. However, the customization of these design systems is increasing.


Write A Comment