A tab bar represents "which top-level section am I in," not a screen you navigate to. So tapping a tab shouldn't push a new screen — each tab keeps its own content, scroll position, and navigation stack alive independently, and switching just changes which one is visible (commonly by toggling `display` or stacking views). That way scrolling down the home tab, visiting search, and coming back leaves the scroll position untouched.
iOS calls this a Tab Bar, managed by `UITabBarController`; Android calls it Bottom Navigation, managed by Material's `BottomNavigationView`. The name and fine print — icon size, badge placement, item limits — differ by platform, but the role is the same: an always-visible top-level table of contents.
Past five items the icons get cramped and any single tab becomes hard to read at a glance. Rather than bundling the overflow into a "more" tab, it's usually better to keep only what's genuinely used often on the bar and move the rest somewhere else — settings, a profile menu.
When to use
Use it for an app with 3–5 top-level sections spanning the whole experience — home, search, notifications, profile. For switching sub-categories within a single screen, a segmented control fits better.