YouTube2Text

Top UI/UX Design Tips - How to Design a Great Bottom Mobile Navigation Bar — Transcript

by uxpeak · 4,003 words · 626 segments · language en · Watch on YouTube

Full transcript

  1. 0:00If your bottom navigation looks like
  2. 0:01this or this or even this, you need to
  3. 0:05watch this video because right now your
  4. 0:07users are probably suffering. Every time
  5. 0:10they open your app, they feel like this.
  6. 0:13A bad bottom navigation doesn't just
  7. 0:15look messy and unappealing. It makes
  8. 0:17your app frustrating to use and
  9. 0:19confusing to navigate. And when that
  10. 0:21happens, users don't just get annoyed,
  11. 0:24they leave and find something better.
  12. 0:26But here's the good news. Fixing this is
  13. 0:29easier than you think if you know the
  14. 0:31right UI design principles. And today
  15. 0:33I'm going to show you exactly how to
  16. 0:35design a bottom navigation bar that's
  17. 0:37not just good, but so intuitive and
  18. 0:40smooth that people will love using your
  19. 0:42app. These are the same design
  20. 0:44principles used by the best apps in the
  21. 0:46world. And by the end of this video,
  22. 0:48you'll know exactly how to design a
  23. 0:50bottom navbar that feels amazing. Oh,
  24. 0:54and stick around till the end because
  25. 0:55there's one big mistake that even pro
  26. 0:58designers keep making. And trust me, you
  27. 1:00don't want to be that designer. Now, one
  28. 1:04thing that can really take your bottom
  29. 1:05navigation to the next level is adding
  30. 1:07subtle micro interactions like this.
  31. 1:10Looks great, right? It's those small
  32. 1:12details that make an app feel polished
  33. 1:14and responsive. But before you get too
  34. 1:17excited about animations, there's
  35. 1:19something even more important. the
  36. 1:22fundamentals because if you don't get
  37. 1:24the basics right, no amount of fancy
  38. 1:27micro interactions will save your
  39. 1:29navigation. So, let's start from the
  40. 1:31ground up. When you open a mobile app,
  41. 1:33you'll usually see two types of
  42. 1:35navigation. Top navigation, which sits
  43. 1:38at the top, and bottom navigation, which
  44. 1:40sits at the bottom of your screen. They
  45. 1:42look similar on both iOS and Android.
  46. 1:45But here's something that confuses a lot
  47. 1:47of designers. On iOS, it's called a tab
  48. 1:50bar. On Android, it's called bottom
  49. 1:52navigation. Throughout this video, I'll
  50. 1:54just call it the bottom navigation bar
  51. 1:56to keep it simple. Now, a lot of
  52. 1:58designers think the bottom navigation
  53. 2:00bar is just buttons at the bottom, but
  54. 2:02the truth is it's so much more. It's
  55. 2:05actually the backbone of your app's
  56. 2:07usability. Here's why. Your bottom
  57. 2:09navigation bar represents the top level
  58. 2:12structure of your app. It tells users
  59. 2:14what's important and helps them move
  60. 2:15quickly between the core sections. And
  61. 2:17here's something you really need to
  62. 2:19understand. This is prime real estate.
  63. 2:23Your bottom navigation is one of the
  64. 2:24most tapped, most used areas in your
  65. 2:27entire app. So, every icon, every label,
  66. 2:31every micro interaction, you have to be
  67. 2:33strategic because a well-designed bottom
  68. 2:36navigation can make your app feel
  69. 2:38effortless. A bad one, it drives people
  70. 2:41away. So, how do you decide what to put
  71. 2:44in your bottom navigation bar? Let's
  72. 2:46break it down step by step. Tip:
  73. 2:48Prioritize the most important and
  74. 2:50frequently used screens or actions. The
  75. 2:53bottom navigation should only contain
  76. 2:55the most essential destinations in your
  77. 2:57app. The core features users interact
  78. 3:00with most often. Good candidates for
  79. 3:02bottomnav. Home, main feed, dashboard,
  80. 3:05or landing screen. Search, discover, if
  81. 3:08users frequently search or browse
  82. 3:09content. Add, create, if users regularly
  83. 3:13add posts, messages, or content.
  84. 3:15Messages, notifications. If social
  85. 3:17interaction is a big part of the app,
  86. 3:20profile, user account settings, history,
  87. 3:22and saved content. Bad candidates for
  88. 3:25bottomnav. Help. Fact. It needs to be in
  89. 3:28profile or side menu. Log out. No one
  90. 3:31logs out that frequently. Keep it
  91. 3:33elsewhere. Legal pages, privacy policy,
  92. 3:36terms, etc. Nobody needs these at their
  93. 3:38fingertips. Introducing elements like a
  94. 3:40back or forward button or even logos
  95. 3:42which are traditionally part of the top
  96. 3:44navigation in the bottom navigation bar
  97. 3:46is a practice best avoided. This
  98. 3:49approach aligns with Jacob's law which
  99. 3:51suggests that users spend most of their
  100. 3:53time on other websites or apps.
  101. 3:55Therefore, they prefer your site or app
  102. 3:57to work the same way as others they
  103. 3:59already know. Cluttering the bottom
  104. 4:00navigation with elements typically found
  105. 4:02at the top can confuse users as it goes
  106. 4:05against the familiar navigation patterns
  107. 4:07they're accustomed to. On the other
  108. 4:09hand, including a call toaction CTA
  109. 4:12button in the bottom navigation is a
  110. 4:14smart move. These buttons are usually
  111. 4:16placed in the center of prominence and
  112. 4:18ease of access. CTAs like create an
  113. 4:21order or post serve a dual purpose. They
  114. 4:24stand out to the user, encouraging
  115. 4:26action, and their central positioning
  116. 4:28makes them easily reachable, especially
  117. 4:30on larger devices. Tip: Understand who
  118. 4:33are your users before you design
  119. 4:35anything, especially your bottom
  120. 4:37navigation. You need to know who your
  121. 4:39users are, who's your target audience
  122. 4:41because this will shape everything about
  123. 4:43your design choices. Ask yourself, how
  124. 4:46comfortable are they with technology?
  125. 4:47How old are they? What problems are you
  126. 4:50helping them solve? What devices do they
  127. 4:52use? Why does this matter? Because even
  128. 4:55small decisions like adding labels to
  129. 4:57your icons depend on your users. If your
  130. 5:00audience is younger and techsavvy, you
  131. 5:02might get away with minimalist approach
  132. 5:04and show just icons. But if your users
  133. 5:07are older and less familiar with apps,
  134. 5:09labels below icons can make navigation
  135. 5:12clearer and help them feel more
  136. 5:13confident using your app. Tip: Choose
  137. 5:16the right sizes, padding, and margins.
  138. 5:19Creating the right autonomy for your
  139. 5:20bottom navigation is like crafting a
  140. 5:22tailorade suit. It needs to fit
  141. 5:25perfectly with the device it's designed
  142. 5:26for. In the image, you can see detailed
  143. 5:29properties for navigation on the iPhone
  144. 5:3114 and iPhone 15 Pro. But these are
  145. 5:34guidelines, not rigid rules. The key is
  146. 5:37to adapt and experiment to find what
  147. 5:39works best for each device. Why does
  148. 5:42this matter? Well, on smaller devices, a
  149. 5:44more compact navigation bar might be
  150. 5:46more appropriate. A bulky bar can eat up
  151. 5:49valuable screen space, making the app
  152. 5:51feel cramped. The goal is to find the
  153. 5:53right balance between visibility and
  154. 5:55accessibility without overshadowing the
  155. 5:58main content. Generally, an icon size of
  156. 6:0124 pixels strikes a good balance. It's
  157. 6:03large enough to be recognizable but
  158. 6:05doesn't dominate the screen. The home
  159. 6:07indicator, that dark bar at the bottom,
  160. 6:09typically takes up around 34 pixels.
  161. 6:12When it comes to labels, the sweet spot
  162. 6:14is around 10 to 12 pixels. Smaller text
  163. 6:17can cause accessibility issues, making
  164. 6:19it hard for some users to read. On the
  165. 6:21flip side, larger text can create
  166. 6:24clutter and draw attention away from the
  167. 6:25main content. Remember, labels are there
  168. 6:28to guide, not to overshadow. Designing
  169. 6:31for two to three mobile device widths is
  170. 6:33a good practice. It ensures your
  171. 6:35navigation bar looks great and functions
  172. 6:37well across a range of devices. If
  173. 6:39you're designing a bottom navigation bar
  174. 6:41for modern smartphones, especially on
  175. 6:43iPhones and Android devices without
  176. 6:45physical buttons, there's one detail
  177. 6:47that many junior designers forget. the
  178. 6:50home indicator. That thin line at the
  179. 6:53bottom of the screen, that's the home
  180. 6:55indicator. It lets users swipe up to go
  181. 6:57back to the home screen, and it sits
  182. 6:59right below your bottom navigation bar.
  183. 7:02So, here's what you need to know. You
  184. 7:04should not modify or hide the home
  185. 7:07indicator. You should not overlap your
  186. 7:10navigation bar onto it. Why does this
  187. 7:12matter? Because if your bottom
  188. 7:14navigation is too low or feels cramped
  189. 7:16against the home indicator, users might
  190. 7:19accidentally trigger the home indicator
  191. 7:21when trying to tap your nav icons. Find
  192. 7:23your app harder to use, especially
  193. 7:25one-handed. Feel like your design is
  194. 7:27broken or unfinished. What to do
  195. 7:30instead? Respect the devices safe area,
  196. 7:33also called the safe zone. Make sure
  197. 7:35your bottom navigation sits above the
  198. 7:37home indicator so there's enough
  199. 7:39spacing. Test it on a real device. Use
  200. 7:42Figma Mirror to see your design directly
  201. 7:44on your phone. What looks good in Figma
  202. 7:47on your screen can feel completely
  203. 7:49different when you're actually tapping
  204. 7:50it on a real phone. Tip: Limit the
  205. 7:53number of tabs to five. Having too many
  206. 7:56tabs in the bottom navigation can lead
  207. 7:58to a cluttered and confusing user
  208. 8:00experience. Overloading the space with
  209. 8:02excessive options not only makes each
  210. 8:04tab smaller and harder to accurately
  211. 8:06tap, especially on mobile devices, but
  212. 8:09also overwhelms users with too many
  213. 8:11choices. This can lead to what's known
  214. 8:13as choice paralysis, where users find it
  215. 8:16difficult to make a decision because of
  216. 8:17the sheer number of options presented to
  217. 8:20them. The golden rule, aim for three to
  218. 8:22five tabs, max six tabs. This range is
  219. 8:26the sweet spot for bottom navigation. It
  220. 8:28gives users enough options without
  221. 8:30crowding the space. With fewer tabs,
  222. 8:32each one has more breathing room, making
  223. 8:34them easier to tap and reducing
  224. 8:36accidental clicks. This also makes your
  225. 8:38app feel more organized and easier to
  226. 8:41navigate. Focus on what matters most.
  227. 8:43Choose tabs that are essential to your
  228. 8:45app's core functions and what users
  229. 8:47access most often. This way, your users
  230. 8:50have everything they need at their
  231. 8:52fingertip without the extra clutter.
  232. 8:54Tip: Design thumb friendly tap areas. A
  233. 8:58common convention is to use a tap area
  234. 9:00that is large enough to be easily tapped
  235. 9:02with a thumb. This usually means having
  236. 9:04a tap area of at least 44 pixels x 44
  237. 9:07pixels. This size is not just a random
  238. 9:09choice. It's based on the average size
  239. 9:11of a human thumb, which ensures that
  240. 9:13most users can comfortably and
  241. 9:15accurately tap the navigation items
  242. 9:17without accidentally hitting the wrong
  243. 9:19one. Why is this important? First, it
  244. 9:22improves the overall usability of your
  245. 9:24app. Users are likely to navigate using
  246. 9:26their thumbs, especially on smaller
  247. 9:28devices. A larger tap area reduces the
  248. 9:31chance of errors and frustration, making
  249. 9:33the app more userfriendly. Second, it
  250. 9:36enhances accessibility. Not all users
  251. 9:38have the same level of dexterity, and a
  252. 9:41generous tap area ensures that the app
  253. 9:43is more accessible to people with
  254. 9:44varying motor abilities. In contrast, a
  255. 9:47smaller tap area, like 24 pixels x 24
  256. 9:51pixels, might lead to frequent mistaps
  257. 9:53and a poor user experience. Enjoying the
  258. 9:56tips so far? That's awesome. But let's
  259. 9:58be real, watching a few tips is great,
  260. 10:01but what is really going to make a
  261. 10:02difference is knowing how to put it all
  262. 10:04together. That's where a lot of
  263. 10:06designers get stuck. You pick up bits
  264. 10:08and pieces, but when you sit down to
  265. 10:10design, something still feels off.
  266. 10:12That's exactly why we created the UIUX
  267. 10:15playbook to give you clear, practical
  268. 10:17techniques and real examples that show
  269. 10:19you how to design UIs that look clean,
  270. 10:21modern, and professional so your work
  271. 10:24stands out and looks right every time.
  272. 10:26We've had so much amazing feedback from
  273. 10:28designers who said that after reading
  274. 10:30the playbook, they went from struggling
  275. 10:32with designs that just didn't look right
  276. 10:34to creating work that looks amazing and
  277. 10:37that they're finally proud to share. If
  278. 10:39you want to check it out, there's a
  279. 10:40special discount for you. Use level up
  280. 10:4240 at checkout to get 40% off. And if
  281. 10:45you're curious, you can also download a
  282. 10:47free preview first. You'll find
  283. 10:49everything linked in the description
  284. 10:51below. Tip: Differentiate active and
  285. 10:54inactive states. Differentiating the
  286. 10:56active state in bottom navigation is
  287. 10:58essential for creating a clean user
  288. 11:00experience. It's about making it
  289. 11:02immediately obvious to the user where
  290. 11:04they are in the app. A smart way to do
  291. 11:06this is to change the style and color of
  292. 11:08the active icon. Imagine an icon that
  293. 11:11shifts from an outline to a filled
  294. 11:13version along with a noticeable change
  295. 11:14in color. This visual cue instantly
  296. 11:17draws the user's attention to their
  297. 11:19current location. To further enhance
  298. 11:21this distinction, you can also make the
  299. 11:23labeled text for the active icon darker
  300. 11:25and thicker. This simple adjustment
  301. 11:28reinforces the user's focus on the
  302. 11:29active state. The combination of a
  303. 11:32transformed icon style, a standout
  304. 11:34color, and bolder text works effectively
  305. 11:37to differentiate the active tab from the
  306. 11:39inactive ones. Conversely, a design that
  307. 11:42only alters the text, leaving the icon
  308. 11:44unchanged, might not be distinct enough.
  309. 11:47In such cases, users might take longer
  310. 11:49to identify their current position in
  311. 11:51the app, potentially leading to a slower
  312. 11:53and more frustrating navigation
  313. 11:55experience. It's important to strike a
  314. 11:57balance and ensure that the active state
  315. 11:59stands out clearly for effortless
  316. 12:01navigation. It's also perfectly
  317. 12:03acceptable to keep the icon outlined
  318. 12:05instead of filling it in as long as you
  319. 12:07change its color. The key is to apply at
  320. 12:09least two visual changes, such as
  321. 12:12adjusting the icon's color and making
  322. 12:14the text bolder. This dual change
  323. 12:16ensures users can effortlessly
  324. 12:18distinguish between active and inactive
  325. 12:20tabs, enhancing their navigation
  326. 12:22experience in your app. Tip: Choose
  327. 12:25simple and familiar icons. When
  328. 12:28selecting icons for your bottom
  329. 12:29navigation bar, the best approach is to
  330. 12:32prioritize familiarity and simplicity.
  331. 12:35Choose icons that users can instantly
  332. 12:37recognize and that accurately represent
  333. 12:39their function. A classic example is
  334. 12:41using a magnifying glass for the search
  335. 12:43function. It's a universally understood
  336. 12:46symbol, making it far more effective
  337. 12:48than less familiar options like
  338. 12:50binoculars. The simplicity of each icon
  339. 12:52is also key. Complex designs or overly
  340. 12:55artistic interpretations can confuse
  341. 12:57users. The goal is to enable users to
  342. 13:00understand and navigate your app with
  343. 13:02minimal effort or thought. Simple icons
  344. 13:04achieve this by being easy to identify
  345. 13:06at a glance. Tip: Keep navigation labels
  346. 13:10short and sweet. When it comes to
  347. 13:12designing your bottom navigation bar,
  348. 13:14less is often more. Opt for concise
  349. 13:17single line labels to keep the design
  350. 13:20neat and effective. Avoid long labels
  351. 13:22that spill over into two lines. They can
  352. 13:25clutter the screen and overwhelm your
  353. 13:27users. They also tend to make the
  354. 13:29navigation bar too big, which can throw
  355. 13:31off the balance of your app's layout.
  356. 13:33Short labels keep things simple, helping
  357. 13:35users make quicker, more instinctive
  358. 13:37choices. They also contribute to a
  359. 13:40clean, contemporary aesthetic, ensuring
  360. 13:42your app is both stylish and functional.
  361. 13:45Tip: Keep it clean and simple. A
  362. 13:48cluttered or overwhelming design can
  363. 13:50hurt the user experience. Avoid adding
  364. 13:52unnecessary elements like boxes around
  365. 13:54your tabs as these can create visual
  366. 13:57noise. Instead, strive for a clean,
  367. 14:00minimalist look that guides users
  368. 14:02effortlessly through your app. The goal
  369. 14:04is to design a navigation bar that's
  370. 14:06intuitive and unobtrusive, allowing
  371. 14:08users to focus on what matters most, the
  372. 14:11content of your app. Tip: Stick to one
  373. 14:13icon style except for the selected
  374. 14:15state. Mixing filled and outline icons
  375. 14:18in the same navigation bar is like
  376. 14:20inviting guests to a black tie event
  377. 14:22only to have someone show up in
  378. 14:23beachwear. To avoid this visual
  379. 14:25mismatch, stick to a consistent style of
  380. 14:28icons throughout your navigation. If you
  381. 14:29decide on outline icons, use them
  382. 14:31consistently across all tabs. This
  383. 14:34creates a harmonious and visually
  384. 14:36balanced look. However, there's a clever
  385. 14:38exception, the selected state. here.
  386. 14:41Switching an outline icon to a filled
  387. 14:43version is a fantastic way to highlight
  388. 14:45the active tab. It's like giving that
  389. 14:47tab a special badge of honor, making it
  390. 14:50stand out in a subtle yet effective way.
  391. 14:53Also, be mindful of the complexity of
  392. 14:55your icons. Consistency isn't just about
  393. 14:58style, it's also about complexity. If
  394. 15:01one icon is simple and clean, the others
  395. 15:03should follow suit. Mixing a minimal
  396. 15:06icon with a more detailed one can throw
  397. 15:08off the visual harmony of your
  398. 15:09navigation bar. Tip: Avoid using too
  399. 15:13many colors. Using too many colors in
  400. 15:15your bottom navigation or giving each
  401. 15:17tab its own color may seem like a fun
  402. 15:20idea, but it usually does more harm than
  403. 15:22good. Instead of helping users, it
  404. 15:25creates visual chaos. Suddenly,
  405. 15:27navigation becomes a guessing game of
  406. 15:29colors rather than something that feels
  407. 15:31natural and easy. Here's the thing. You
  408. 15:34want your navigation to feel like part
  409. 15:35of the app, seamless, not loud. When
  410. 15:38every tab is a different color, it pulls
  411. 15:40attention away from what actually
  412. 15:42matters, the content. It can even mess
  413. 15:44with your brand's look, making your app
  414. 15:47feel less polished and harder to
  415. 15:49recognize. The better approach, stick to
  416. 15:51your brand's color palette. Keep it
  417. 15:53simple and consistent. That way, your
  418. 15:56navigation feels clean, your app feels
  419. 15:58professional, and your brand stays
  420. 16:00strong. Tip: Use notification badges in
  421. 16:04bottom navigation to highlight updates.
  422. 16:06Using notification badges in your bottom
  423. 16:08navigation bar is a great way to signal
  424. 16:10new updates or messages to users. These
  425. 16:13badges can be simple colored circles, or
  426. 16:16they can include numbers to indicate the
  427. 16:17quantity of new updates. Badges should
  428. 16:20be small enough to stay subtle, but
  429. 16:22large enough to be noticeable. Placing
  430. 16:24them in the top right corner of the icon
  431. 16:26is a common practice, as it's naturally
  432. 16:28eye-catching. Here's a pro tip. Adding
  433. 16:31an outline around the badge can make it
  434. 16:33stand out even more and give it a
  435. 16:35polished look. If you're using numbers
  436. 16:37within the badge to indicate the count
  437. 16:38of new updates, ensure they are easy to
  438. 16:41read. Avoid overly small or stylized
  439. 16:44fonts that might be hard to decipher at
  440. 16:46a glance. Choose a badge color that
  441. 16:48stands out against the navigation bar
  442. 16:50and icon colors, yet still feels
  443. 16:53consistent with the overall app design.
  444. 16:55Finally, only use badges for essential
  445. 16:58notifications. Overloading users with
  446. 17:00badges for every minor update can lead
  447. 17:03to notification fatigue, reducing the
  448. 17:05effectiveness of this feature. Tip:
  449. 17:08Experiment with creative layouts, but
  450. 17:10with usability being your priority.
  451. 17:12While standard layouts are tried and
  452. 17:14tested for usability, stepping outside
  453. 17:16the box with a creative and beautiful
  454. 17:18design can give your app a distinctive
  455. 17:20edge. The key is to strike a balance
  456. 17:23between aesthetics and usability. You
  457. 17:25can add value to your app by
  458. 17:27experimenting with different shapes,
  459. 17:29positions, or even dynamic interactions
  460. 17:31for your bottom navigation. Maybe you're
  461. 17:33thinking about a unique icon arrangement
  462. 17:35or an unconventional bar shape. These
  463. 17:38creative touches can make your app
  464. 17:40memorable. However, here's a word of
  465. 17:42caution. Never sacrifice usability for
  466. 17:45aesthetics. For instance, while an
  467. 17:47unconventional layout may look stunning,
  468. 17:49if it confuses users or makes navigation
  469. 17:52harder, it can do more harm than good.
  470. 17:54All right, let's make this a little bit
  471. 17:55more interactive. I want you to pause
  472. 17:57the video right now and head to the
  473. 17:59comment section. Tell me which bottom
  474. 18:01navigation design you like the most. Is
  475. 18:03it option A, clean and simple? Option B,
  476. 18:07with that sleek line above the active
  477. 18:08tab, option C, minimalist with a smooth,
  478. 18:11interactive feel, or option D with a
  479. 18:14more distinctive custom look. Drop your
  480. 18:17favorites in the comments, A, B, C, or
  481. 18:19D, and tell me why. I'm curious to see
  482. 18:21which style you prefer.
  483. 18:23Tip: Separate bottom navigation from
  484. 18:26main content. Remember when I mentioned
  485. 18:28you should stick around till the end
  486. 18:30because there's one big mistake that
  487. 18:31even pro designers keep making? Well,
  488. 18:34here it is. Not separating the bottom
  489. 18:36navigation from the main content. Adding
  490. 18:38a subtle soft outline or a one pixel
  491. 18:41border around the navigation bar can
  492. 18:43create a gentle but clear separation.
  493. 18:46This method is unobtrusive yet effective
  494. 18:48at visually distinguishing the
  495. 18:50navigation area as a distinct element.
  496. 18:53Tip: You can use background color to
  497. 18:55separate bottom navigation from main
  498. 18:56content. Another approach is to
  499. 18:58differentiate the background colors of
  500. 19:00the bottom navigation and the main
  501. 19:02screen. For instance, if your main
  502. 19:04screen is white, consider using a light
  503. 19:06gray for the navigation bar. This
  504. 19:08contrast creates a sense of depth,
  505. 19:10making the navigation area feel like a
  506. 19:12distinct interactive element of the app.
  507. 19:16Using a shadow is also a great way to
  508. 19:18achieve this separation. A small soft
  509. 19:20shadow above the navigation bar can
  510. 19:22create an elevated effect, giving the
  511. 19:25impression that the navigation is
  512. 19:26floating above the rest of the content.
  513. 19:28However, it's important to keep the
  514. 19:30shadow subtle. An overly large or harsh
  515. 19:33shadow can draw attention away from the
  516. 19:35content and detract from the sleekness
  517. 19:36of your design. Tip: Choose neutral
  518. 19:39colors and avoid using too many colors
  519. 19:41in both your top and bottom navigation.
  520. 19:44It's best to keep the navigation colors
  521. 19:46neutral, such as white, gray, or dark
  522. 19:48tones. This approach ensures that the
  523. 19:50navigation doesn't distract from the
  524. 19:52main content of the app. By reserving
  525. 19:54brighter or primary colors for key
  526. 19:57actions on the main screen, you help
  527. 19:59those elements stand out and draw
  528. 20:01attention to what matters most. It's
  529. 20:03also important to avoid using too many
  530. 20:05different colors between the top and
  531. 20:06bottom navigation bars. This can lead to
  532. 20:09a disjointed visual experience and
  533. 20:11distract users from the app's content.
  534. 20:13Keeping a consistent color palette
  535. 20:15between these two elements creates a
  536. 20:17cohesive and harmonous design. When
  537. 20:19choosing colors for your navigation,
  538. 20:21it's crucial to consider how they
  539. 20:23complement your app's overall theme and
  540. 20:25branding. While neutral colors like
  541. 20:27white, gray, or dark shades are
  542. 20:29generally recommended for their
  543. 20:31versatility and subtlety, it's perfectly
  544. 20:33fine to opt for a different color if it
  545. 20:35enhances your brand's identity. However,
  546. 20:38the color should not be so bright or
  547. 20:40overpowering that it overwhelms the main
  548. 20:42content or disrupts the user's focus. It
  549. 20:45should complement the primary colors
  550. 20:46used on the main screen, enhancing key
  551. 20:49actions and content rather than
  552. 20:50competing with them. By the way,
  553. 20:53everything that you have learned so far
  554. 20:54here is from our UX UI design mastery
  555. 20:57course, where we have more than 50
  556. 20:59lessons like this one, all designed to
  557. 21:01take you from a beginner to a UX UI
  558. 21:04design pro. If you want to know more,
  559. 21:06the link's in the description. Tip:
  560. 21:08Avoid poor contrast for inactive states.
  561. 21:11A common pitfall is using poor contrast
  562. 21:14for inactive icons and labels, making
  563. 21:16them difficult to see or understand,
  564. 21:18especially for users with visual
  565. 21:20impairments. It's important to strike a
  566. 21:22balance between visibility and
  567. 21:24distinction. Instead of opting for
  568. 21:26drastically different colors, consider
  569. 21:28slightly reducing the opacity of
  570. 21:30inactive elements. This approach
  571. 21:32maintains a cohesive color scheme while
  572. 21:34clearly differentiating active and
  573. 21:36inactive states. A good starting point
  574. 21:39is to aim for an opacity level that is
  575. 21:41noticeable yet not too faint. The web
  576. 21:44content accessibility guidelines
  577. 21:46recommend a minimum contrast ratio of
  578. 21:483:1 for graphical elements and user
  579. 21:50interface components. To make sure your
  580. 21:52color choices meet accessibility
  581. 21:54standards, use tools like the web aim
  582. 21:57contrast checker. Tip: Add sleek micro
  583. 22:01interactions. Now that you mastered all
  584. 22:03important fundamentals and your bottom
  585. 22:05navigation bar has a solid base, it's
  586. 22:08time to take it completely to the next
  587. 22:10level to absolutely delight your users
  588. 22:12and make them go, "Wow!" A lot of
  589. 22:14beginner designers skip this. Their
  590. 22:16bottom navigation is just static. You
  591. 22:19tap and it changes, but there's no
  592. 22:21feeling. It's like pressing a light
  593. 22:23switch with no click. Micro interactions
  594. 22:26and smooth transitions make your bottom
  595. 22:28navigation feel responsive, polished,
  596. 22:30and honestly just more fun to use. Tip
  597. 22:33one, tap feedback. When a user taps an
  598. 22:36icon, show a quick visual response like
  599. 22:38a color change, scale up, or a ripple
  600. 22:41effect. Tip two, when switching between
  601. 22:44tabs, don't just snap to the next one.
  602. 22:46Add a small sliding underline or animate
  603. 22:48the icon smoothly into place. Tip three,
  604. 22:52transitions between screens. When a user
  605. 22:54switches screens, don't make it feel
  606. 22:56like they teleported, add a soft fade,
  607. 22:59or a sides slide transition. It makes
  608. 23:01navigation feel connected. These little
  609. 23:04details, they're what separating boring
  610. 23:06designs from apps that feel amazing. So,
  611. 23:09next time you design a bottom
  612. 23:11navigation, don't just make it work,
  613. 23:14make it feel great. If you made it all
  614. 23:16the way to the end, congratulations. You
  615. 23:19now know how to design a perfect bottom
  616. 23:21navigation bar. and hopefully your
  617. 23:24navigation will never look like this
  618. 23:26ever again. I really hope you enjoyed
  619. 23:29this video. If you did, it would mean a
  620. 23:31lot if you shared it with others. Let's
  621. 23:33make every bottom navigation bar out
  622. 23:35there awesome. Also, let me know in the
  623. 23:37comments which tip was your favorite.
  624. 23:39I'd love to hear what you found most
  625. 23:40helpful. Thanks for watching and I'll
  626. 23:42see you in the next one. Have an amazing

About this transcript

This page contains the full transcript of Top UI/UX Design Tips - How to Design a Great Bottom Mobile Navigation Bar by uxpeak, generated from the public captions YouTube serves with the video. The transcript has 4,003 words across 626 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to translate the transcript into 100+ languages.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, translation to 100+ languages, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.