Skip to main content

3 Creative Concepts of Mobile Tab Bar Navigation

3 Creative Concepts of Mobile Tab Bar Navigation


When it comes to selecting a pattern for the primary mobile navigation, product designers usually choose between two options — side drawer (also known as a hamburger menu) and tab bar. Both navigation patterns have their pros and cons.
Tab bar vs. Side drawer (hamburger menu). Image: Google
Since this article is about tab bar, let’s start with its advantages over sider drawer:
  • Visibility of current user location. No need to tap on a hamburger menu to find out where you are in the app. It’s possible to get this information in a glance.
  • Good discoverability. Users see all top-level navigation options right from the start.
  • Thumb-friendly. Tab bar is located in easy to reach zone (bottom of the screen). Users don’t need to stretch fingers to reach a particular option.
But tab bar also has a few downsides:
  • Limited number of navigation options. It’s possible to place from five to seven navigation options in the tab bar without making the size of the touch target too tiny.
  • Tab bar takes a part of the screen. Since good navigation should be visible all the time, tab bar will take a part of the valuable screen space.
In this article, you’ll find three interesting concepts of tab bar navigation. I also provide links to the source code so you can use some of those concepts in your projects.

1. Nested navigation options

As was mentioned above, one of the significant downsides of tab bar is a limited number of options. On mobile phones, it’s possible to place a maximum seven top-level navigation options in a tab bar. While the limited number of navigation options won’t be a problem for a vast majority of mobile apps, some apps might need to provide more options.
Below you can find a concept that tries to solve a problem of a limited number of options. When users tap on a folder icon, a few more options become visible in the same physical space. The size of a folder icon (the one that acts as a parent for other three option) implies that this object does more than other options for users.
Pros: Provide more options in the same physical space.
Cons:
  • Animated effects might require extra development time.
  • High interaction cost. Extra tap required to select a nested option.

2. Separating the active tab button from the tab bar

Since tab bar usually has top-level navigation options, each option in a bar acts as an independent destination. The concept demonstrated below tries to separate the targets visually.
Ketan (the author of this animation) provides the source code of this animated bar React Native Tabbar Interaction. He also describes a process of creation of this bar in details in his article FAB Tabbar — Concept to Reality
  • Pros: Nice visual transition clearly distinguishes source and destination.
  • Cons: An animation feels a bit slow. This can be annoying especially when you have to constantly switch between the tabs to interact with an app.

3. Animated effects on tap

Creating good first impression is one of the most important goals mobile developers have today. Considering the fact that an average app loses 80% of their users soon after the installation, creating a good impression is a chance to reduce this percentage.
One of the ways to achieve this goal is to create a memorable experience. When we interact with a digital product we don’t remember the entire process of interaction, what we usually remember are specific details. This might be something as simple as a funny mascot, vibrant colors or fine animation. That’s why many designers say over and over again that
Smooth animated effects which are used in the following concept are able to create a truly memorable first-time experience. Ramotion (the author of this concept) provides source code for this animation.
  • Pros: Animated effect helps to create a good first impression.
  • Cons: Animated effects can be annoying for regular users. Just imagine users who see such effects each time when they interact with an app.

Do you have some interesting concept that you want to share with us? Share it in the comment section!

Comments

Post a Comment

Thank You.

Popular Posts

Reloading UITableView while Animating Scroll in iOS 11

Reloading UITableView while Animating Scroll Calling  reloadData  on  UITableView  may not be the most efficient way to update your cells, but sometimes it’s easier to ensure the data you are storing is in sync with what your  UITableView  is showing. In iOS 10  reloadData  could be called at any time and it would not affect the scrolling UI of  UITableView . However, in iOS 11 calling  reloadData  while your  UITableView  is animating scrolling causes the  UITableView  to stop its scroll animation and not complete. We noticed this is only true for scroll animations triggered via one of the  UITableView  methods (such as  scrollToRow(at:at:animated:) ) and not for scroll animations caused by user interaction. This can be an issue when server responses trigger a  reloadData  call since they can happen at any moment, possibly when scroll animation is occurring. Example of s...
Post a Comment
Read more

What are the Alternatives of device UDID in iOS? - iOS7 / iOS 6 / iOS 5 – Get Device Unique Identifier UDID

Get Device Unique Identifier UDID Following code will help you to get the unique-device-identifier known as UDID. No matter what iOS user is using, you can get the UDID of the current iOS device by following code. - ( NSString *)UDID { NSString *uuidString = nil ; // get os version NSUInteger currentOSVersion = [[[[[UIDevice currentDevice ] systemVersion ] componentsSeparatedByString: @" . " ] objectAtIndex: 0 ] integerValue ]; if (currentOSVersion <= 5 ) { if ([[ NSUserDefaults standardUserDefaults ] valueForKey: @" udid " ]) { uuidString = [[ NSUserDefaults standardDefaults ] valueForKey: @" udid " ]; } else { CFUUIDRef uuidRef = CFUUIDCreate ( kCFAllocatorDefault ); uuidString = ( NSString *) CFBridgingRelease ( CFUUIDCreateString ( NULL ,uuidRef)); CFRelease (uuidRef); [[ NSUserDefaults standardUserDefaults ] setObject: uuidString ForKey: @" udid " ]; [[ NSUserDefaults standardUserDefaults ] synchro...
Post a Comment
Read more

Xcode & Instruments: Measuring Launch time, CPU Usage, Memory Leaks, Energy Impact and Frame Rate

When you’re developing applications for modern mobile devices, it’s vital that you consider the performance footprint that it has on older devices and in less than ideal network conditions. Fortunately Apple provides several powerful tools that enable Engineers to measure, investigate and understand the different performance characteristics of an application running on an iOS device. Recently I spent some time with these tools working to better understand the performance characteristics of an eCommerce application and finding ways that we can optimise the experience for our users. We realised that applications that are increasingly performance intensive, consume excessive amounts of memory, drain battery life and feel uncomfortably slow are less likely to retain users. With the release of iOS 12.0 it’s easier than ever for users to find applications that are consuming the most of their device’s finite amount of resources. Users can now make informed decisions abou...
Post a Comment
Read more