Account search
Account search is a Autocomplete block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
Search boxes over accounts and people, where each row should say at a glance who is who
Anatomy
44px search field with clear, the picked account's tile at its start · list card with Accounts and People groups and counts · monogram tile or face, name with the typed run in bold, industry · contacts · city, Trial or Churned chip · skeleton rows while a new search runs · Create account on a miss · Recent searches and Recently opened when empty · key hints footer · line under the field that says what was opened
In the Orvain Library
Get Account search for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Autocomplete
What’s inside
10parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- 44px search fieldwith clear, the picked account's tile at its start
- List cardwith Accounts and People groups and counts
- Monogram tile or facename with the typed run in bold, industry
- Contacts
- City, Trial or Churned chip
- Skeleton rows while a new search runs
- Create accounton a miss
- Recent searches and Recently opened when empty
- Key hints footer
- Line under the fieldthat says what was opened
Responsive behaviour
420 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
When to use it
Where Autocomplete earns its place
Reach for Autocomplete
- A search box where the reader half-knows the thing they are looking for
- Address or place entry, where the canonical spelling comes from a service
- A setting whose value is one of thousands: timezone, language, currency
- An at-mention inside a composer, offered as the name is typed
Reach for something else
- The set of answers is fixed and modest, like a status or a plan tier: a dropdown states the options instead of waiting for someone to guess a prefix
- The reader is adding entries rather than finding one; a tag input holds a set, while autocomplete returns a single answer
- Results take seconds to arrive: a list that lands after the reader has finished typing is worse than none, so use a search button and a results page
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Account search” block to this page: 44px search field with clear, the picked account's tile at its start, list card with Accounts and People groups and counts, monogram tile or face, name with the typed run in bold, industry, contacts, city, Trial or Churned chip, skeleton rows while a new search runs, Create account on a miss, Recent searches and Recently opened when empty, key hints footer, line under the field that says what was opened.
Questions about Account search.
What is the Account search block?
Account search is a Autocomplete block from Orvain UI, built for React and Vue with a matching Figma frame. Best for search boxes over accounts and people, where each row should say at a glance who is who.
What is the Account search block made of?
10 parts: 44px search field with clear, the picked account's tile at its start; list card with Accounts and People groups and counts; monogram tile or face, name with the typed run in bold, industry; contacts; city, Trial or Churned chip; skeleton rows while a new search runs; create account on a miss; recent searches and Recently opened when empty; key hints footer; and line under the field that says what was opened. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Account search block responsive?
Yes. It is drawn at 420px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Account search block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Account search block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Account search block to this page.”
When should I not use a Autocomplete block?
The set of answers is fixed and modest, like a status or a plan tier: a dropdown states the options instead of waiting for someone to guess a prefix.
More Autocomplete blocks
All AutocompletePremium components,
free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Orvain MCPAccount search
Account search is a Autocomplete block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
Search boxes over accounts and people, where each row should say at a glance who is who
Anatomy
44px search field with clear, the picked account's tile at its start · list card with Accounts and People groups and counts · monogram tile or face, name with the typed run in bold, industry · contacts · city, Trial or Churned chip · skeleton rows while a new search runs · Create account on a miss · Recent searches and Recently opened when empty · key hints footer · line under the field that says what was opened
In the Orvain Library
Get Account search for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Autocomplete
What’s inside
10parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- 44px search fieldwith clear, the picked account's tile at its start
- List cardwith Accounts and People groups and counts
- Monogram tile or facename with the typed run in bold, industry
- Contacts
- City, Trial or Churned chip
- Skeleton rows while a new search runs
- Create accounton a miss
- Recent searches and Recently opened when empty
- Key hints footer
- Line under the fieldthat says what was opened
Responsive behaviour
420 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
When to use it
Where Autocomplete earns its place
Reach for Autocomplete
- A search box where the reader half-knows the thing they are looking for
- Address or place entry, where the canonical spelling comes from a service
- A setting whose value is one of thousands: timezone, language, currency
- An at-mention inside a composer, offered as the name is typed
Reach for something else
- The set of answers is fixed and modest, like a status or a plan tier: a dropdown states the options instead of waiting for someone to guess a prefix
- The reader is adding entries rather than finding one; a tag input holds a set, while autocomplete returns a single answer
- Results take seconds to arrive: a list that lands after the reader has finished typing is worse than none, so use a search button and a results page
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Account search” block to this page: 44px search field with clear, the picked account's tile at its start, list card with Accounts and People groups and counts, monogram tile or face, name with the typed run in bold, industry, contacts, city, Trial or Churned chip, skeleton rows while a new search runs, Create account on a miss, Recent searches and Recently opened when empty, key hints footer, line under the field that says what was opened.
Questions about Account search.
What is the Account search block?
Account search is a Autocomplete block from Orvain UI, built for React and Vue with a matching Figma frame. Best for search boxes over accounts and people, where each row should say at a glance who is who.
What is the Account search block made of?
10 parts: 44px search field with clear, the picked account's tile at its start; list card with Accounts and People groups and counts; monogram tile or face, name with the typed run in bold, industry; contacts; city, Trial or Churned chip; skeleton rows while a new search runs; create account on a miss; recent searches and Recently opened when empty; key hints footer; and line under the field that says what was opened. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Account search block responsive?
Yes. It is drawn at 420px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Account search block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Account search block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Account search block to this page.”
When should I not use a Autocomplete block?
The set of answers is fixed and modest, like a status or a plan tier: a dropdown states the options instead of waiting for someone to guess a prefix.
More Autocomplete blocks
All AutocompletePremium components, free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
