Navigation

TabBarMobile

iOS-style bottom tab bar — fixed at the bottom with icon + label per tab.

Quick Preview

The real component uses position: fixed. This mockup simulates how it looks inside a phone frame.

App content

🏠Home 🔍Explore +Create 🔔Activity 👤Profile

Fixed positioning: TabBarMobile uses position: fixed; bottom: 0. Mount it once at the root layout so it stays at the bottom of the screen across all pages.

Installation

// Copy from
src/components/navigation/TabBarMobile.tsx

Usage

// app/layout.tsx
import TabBarMobile from '@/components/navigation/TabBarMobile'

const tabs = [
  { icon: '🏠', label: 'Home', href: '/' },
  { icon: '🔍', label: 'Explore', href: '/explore' },
  { icon: '+', label: 'Create', href: '/create' },
  { icon: '🔔', label: 'Activity', href: '/activity' },
  { icon: '👤', label: 'Profile', href: '/profile' },
]

export default function RootLayout({ children }) {
  return (
    <html>
      <body className="pb-20 md:pb-0">
        {children}
        <TabBarMobile items={tabs} />
      </body>
    </html>
  )
}

Examples

4-tab layout

Fewer tabs for content-first apps

App content

🏠Home 📚Library 🔔Alerts 👤Me

Prompt Preview

Copy a prompt that recreates this UI

Paste this into your AI coding assistant to generate code that closely matches the reference, including color, size, shape, typography, spacing, and polish.

Copy-ready AI prompt

Starts from the current visual reference and project constraints.

Build a navigation component named TabBarMobile in React/Next.js.
Goal: recreate the same overall UI and behavior as the TabBarMobile reference from a component gallery.
What it needs to communicate: iOS-style bottom tab bar — fixed at the bottom with icon + label per tab..

Project constraints:
- Use Next.js 16.2.6 with the App Router, React 19, TypeScript strict mode, and Tailwind CSS v4.
- Do not create a tailwind.config.js file. Use Tailwind v4 utilities and CSS variables where design tokens are needed.
- If you are implementing this inside the same project, use the Prompt font via next/font/google. If not, use the closest equivalent typeface.
- Return production-ready code with imports, responsive behavior, keyboard accessibility, and polished empty, hover, focus, active, and disabled states where relevant.
- Match the reference closely: color palette, spacing scale, border radius, shadows, icon scale, typography hierarchy, and motion timing.

Component-specific expectations:
- Handle hover, active, selected, keyboard, and mobile states with clear feedback.
- Keep structure tidy so it feels production-ready rather than demo-only.
- Avoid unnecessary dependencies unless the behavior truly requires them.
- No explicit color literals were found in the examples. Match the live reference and the project accent color when appropriate.

Props to support:
- items: TabBarItem[] — required — Array of {icon, label, href}
- activeHref: string — Currently active route href

Reference usage patterns:
- No examples were documented. Infer a sensible default presentation and one richer usage example.

Feature expectations:
- Active state highlight
- Safe area aware
- Icon + label
- Responsive

Output requirements:
- Return complete code, not pseudocode.
- Include all necessary imports and helper types.
- Keep the implementation accessible, responsive, and visually finished.
- Match the reference for color, size, shape, typography, spacing, and interaction states as closely as possible.
- If multiple files are needed, organize them cleanly and explain the file structure briefly.

Tweak only product-specific copy or data after the first generation pass.

Props

Prop	Type	Default	Description
`items`*	`TabBarItem[]`	-	Array of {icon, label, href}
`activeHref`	`string`	-	Currently active route href