App Directory

Browse, search and connect integrations, with counts that follow your search.

PROGet App Directory and 168 other Pro components with pro lifetime — Get Pro

Category
Workspace
Access
Pro
Source
601 lines · one file
States
7 drawn
Added
21 Oct 2026

The decision inside it

Counts are live and honest

Each category shows how many apps match the current search and filters, not how many it holds, so "Billing 0" means exactly that. An empty category greys out instead of disappearing, so the sidebar never reflows under your pointer while you type.

When to use it

Use App Directory for a full integrations page: search, categories with live counts, Connected / Free / Official filters, sorting, and app cards whose Connect opens Integration Picker's connect step in a drawer. To connect one service from a menu use Integration Picker.

Installation

How you get it

Paste this into Claude Code, Cursor, Codex or any coding agent. It installs the file and uses it as it is, instead of writing a new one.

Use Liro's App Directory for this.
Install it: npx shadcn@latest add @liro/app-directory
(the @liro registry is set up in components.json, with LIRO_KEY in .env.local)
Import it from @/components/ui/app-directory.
Do not rewrite or restyle it. Pass my data through its props
and keep its built-in states.

For the full brief with every prop and the mistakes assistants usually make, use Copy prompt above. Pro components install through the @liro registry with your CLI token: see the Namespaced tab.

Usage

app/integrations/page.tsx
import { AppDirectory, type DirectoryApp } from "@/components/ui/app-directory";

const apps: DirectoryApp[] = [
  { id: "canvas", name: "Canvas", category: "Design", vendor: "Canvas Inc.", official: true, permissions: ["Read files"] },
  { id: "ledger", name: "Ledger", category: "Billing", free: true, permissions: [{ label: "Create invoices", access: "write" }] },
];

export function IntegrationsPage({ connected, connect, request }: {
  connected: Record<string, string>;
  connect: (id: string) => Promise<string>;
  request: (name: string) => Promise<void>;
}) {
  return <AppDirectory app={{ name: "Liro" }} apps={apps} connected={connected} onConnect={connect} onRequest={request} />;
}

API reference

“Copy prompt” above puts a full brief on your clipboard, install command, dependencies, props, and the mistakes an assistant usually makes with this component.

Props

Read from the component’s own TypeScript interface when the site is built, so this table cannot drift from the file you install.

TypeNotes
appsDirectoryApp[] Yes–
appIntegrationApp NoYour side of every connection, shown on the dark tile.
categoriesstring[] NoCategory order. Default: the order they first appear in `apps`.
categoryIconsRecord<string, React.ReactNode> NoAn icon per category for the sidebar, e.g. { Design: <PenTool /> }.
connectedConnectedMap NoService id → the account it is connected as. Controlled.
defaultConnectedConnectedMap No–
onConnectedChange(connected: ConnectedMap) => void No–
onConnectConnectHandler No–
onDisconnectDisconnectHandler No–
onRequest(name: string) => void | Promise<void> No"Request it" on an empty search. May return a promise.
querystring No–
defaultQuerystring No–
onQueryChange(query: string) => void No–
categorystring | null NoThe selected category, or null for all apps.
defaultCategorystring | null No–
onCategoryChange(category: string | null) => void No–
filtersDirectoryFilters No–
defaultFiltersDirectoryFilters No–
onFiltersChange(filters: DirectoryFilters) => void No–
sortDirectorySort No–
defaultSortDirectorySort No–
onSortChange(sort: DirectorySort) => void No–
titleReact.ReactNode NoThe page title. Default "Integrations".
descriptionReact.ReactNode NoThe line under the title.
labelReact.ReactNode NoThe small label on the frame. Default "Apps".

Dependencies

npm packages

clsxframer-motionlucide-reacttailwind-merge

Liro foundations, installed alongside it

liro-themebuttondrawerinputintegration-pickerpopover

States

All of them are drawn by the component. None is left for you to design.

  • Browse
  • Searching
  • Filtered
  • Connecting
  • Connected
  • No match
  • Requested

Accessibility

  • Keyboard reachable throughout, in visual order
  • Focus trapped in overlays, Escape closes them
  • Focus returns to whatever opened it
  • Live regions announce what changed, not that something did
  • Honours prefers-reduced-motion

Responsive behavior

  • Sizes to its container, not the viewport
  • Usable from 320px up
  • Pointer-based interaction, so trackpad and touch both work
  • No hover-only affordances

Used in a screenAll screens

ScreenPro

Integrations

Connected tools with their health first: what is broken, what is fine, and a directory to add more.