Navigation

FloatingDock

macOS-inspired icon dock with magnification — icons scale up as you hover.

Quick Preview

Hover over icons to see the magnification effect

Home🏠

Search🔍

Library📚

Favourites⭐

Notifications🔔

Settings⚙️

Profile👤

Installation

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

Usage

import FloatingDock from '@/components/navigation/FloatingDock'

<FloatingDock
  items={[
    { icon: '🏠', label: 'Home', href: '/' },
    { icon: '🔍', label: 'Search', onClick: () => openSearch() },
    { icon: '⚙️', label: 'Settings', href: '/settings' },
  ]}
/>

Examples

Compact — 4 items

Fewer items create a more focused dock

Home🏠

Notes📝

Calendar📅

Trash🗑️

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 FloatingDock in React/Next.js.
Goal: recreate the same overall UI and behavior as the FloatingDock reference from a component gallery.
What it needs to communicate: macOS-inspired icon dock with magnification — icons scale up as you hover..

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: DockItem[] — required — Array of {icon, label, href?, onClick?}

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

Feature expectations:
- Magnification effect
- Label tooltips
- href or onClick
- Smooth spring scaling

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`*	`DockItem[]`	-	Array of {icon, label, href?, onClick?}