Typed Triggers vs Hotkeys vs Search Pickers (2026)

The decision is retrieval, not features

Text expanders fail in the head more often than in the engine. You have the refund paragraph. You cannot remember ;ref2 vs ;refund.

TextExpander’s 2025 product recap named the top user request, by far: “Help me find Snippets faster” (community post, Dec 2025, verified August 2026). Their own best-practice writeup says abbreviations should be short, memorable, and hard to fire by accident, then points at Inline Search when memory fails (abbreviation prefixes; best practices).

Typed triggers, hotkeys, and pickers are three retrieval strategies for the same snippet. Pick by frequency and forgetfulness, not by brand loyalty.

TypeFire’s public guide (another expander) lands on the same split: keyboard shortcuts for the top 5–15 daily snippets, abbreviations for the regular 20–40, launcher/search for the long tail (TypeFire shortcuts guide, verified August 2026). That mix is the useful default even if you never install TypeFire.

At a glance comparison

Typed triggers: fastest when memory holds

A typed trigger (abbreviation, keyword, autotext, hotstring) is a short string the expander watches for, then replaces.

You stay in the sentence. No modal. No mouse. That is why people start with this method, and why it still wins for ;em, :addr, //te.

Costs: You must remember the string. Bare words (angry, addr) expand inside real English. Prefixes (;, :, //, sup.) fix most of that (TE prefix guide). FlitKey’s shipped example uses :gcm for a git commit line (pack JSON in docs).

When it loses: Infrequent snippets. Typos in the trigger. Linux Wayland on FlitKey, where typed keywords are not supported inline. Apps that swallow synthetic keys (see the compatibility guide).

Hotkeys: instant, and you will run out

A hotkey is a chord. Two jobs get mixed:

1. Snippet hotkeys: this one snippet always expands on Ctrl+Alt+F.
2. App hotkeys: open the picker, repeat last expand, toggle expansion. TextExpander’s Inline Search defaults are Command+/ (Mac), Control+/ (Windows), Control+Period (Chrome) (Inline Search; hotkey prefs, verified August 2026).

Snippet hotkeys are unbeatable when you are not already typing: live call, screen share, jumping between tickets. TypeFire’s rule of thumb is 10+ uses per day before a dedicated shortcut is worth memorizing.

The hard cap is the keyboard. Unique, comfortable chords that do not steal Ctrl+C, Alt+Tab, or VS Code’s palette run out fast. Assign five. Maybe fifteen if you are disciplined. Assigning a hotkey to every support macro is how people quit expanders and blame the product.

FlitKey lets a snippet be trigger_type: hotkey instead of keyword. Global hotkeys work on Windows (native hooks) and Linux X11 (xdotool). They do not register on Wayland.

Searchable pickers: the library stays usable

A searchable picker (Inline Search, search bar, Quick Insert, launcher) is one hotkey that searches labels, abbreviations, and content.

TextExpander describes it as the path when you have a large library or cannot remember the abbreviation; the popup appears where you are typing (Inline Search docs). Zapier’s expander guide called the same pattern “inline search” years ago: floating box, type a keyword from the phrase, insert (Zapier).

Tradeoff: You spend a second searching. You never spend a minute reconstructing a template you already wrote. Labels matter here more than clever triggers: Support / refund policy beats xyz12.

FlitKey’s picker is Quick Insert, default Alt+Space on Windows and X11. On Wayland you open it from the app or tray; the snippet copies to the clipboard for paste. That is also the compatibility escape hatch when typed inject fails.

How FlitKey maps onto the three

MIT license, local JSON, no account. Packs and the snippet manager set keyword or hotkey per item; the picker sees the whole library by label.

Honest gaps:

• No TextExpander-style Inline Search AI recommendations.
• No Espanso word: true / regex triggers.
• No macOS build; Mac users keep TE/Espanso/aText.
• Wayland typed + snippet hotkeys are out until a later input path exists.

The pitch is not that FlitKey invented three methods. It is that you get the mix in a visual app without YAML or a $60–$120/user/year seat (TextExpander pricing, verified August 2026).

A working mix (not a purity test)

Linux users on X11: typed + picker is enough; add two hotkeys if chords already live in your fingers.
Linux users on Wayland: skip the keyword debate and learn the picker first.
Windows: all three; still cap hotkeys.
Teams on Mac + mobile: TextExpander’s Inline Search + shared groups still win the org layer.

Hands-on: one snippet, three activations

Same body:

Thanks for the report on {{date}}. Ref: {{clipboard}}

Trigger (FlitKey keyword)

keyword: :fup
Type :fup in the ticket. Expands in place on Windows/X11.

Hotkey

trigger_type: hotkey, chord you actually remember.
Press it with the ticket ID already copied. No abbreviation in the transcript.

Picker

Alt+Space, search follow or report. On Wayland, paste.

Create the keyword first. Bind Alt+Space the same day. Add a hotkey only after you notice yourself hunting for that one reply. Download FlitKey (free).

Frequently asked questions

What is the difference between a typed trigger and a hotkey?

A typed trigger is a string you type in the text field (;sig). A hotkey is a key combination that fires without that string. FlitKey supports both per snippet.

Should I assign a hotkey to every snippet?

No. Chords collide and you will forget them. Cap snippet hotkeys; put the rest on prefixes and the picker.

When should I use a searchable picker instead of a trigger?

Whenever you cannot remember the abbreviation, the library is large, typed expansion is blocked (some apps, FlitKey on Wayland), or the snippet is rare.

Does FlitKey include a picker like TextExpander Inline Search?

Yes, Quick Insert (Alt+Space on Windows/X11). Same job: search and insert without memorizing the keyword. TE’s defaults are Cmd+/ or Ctrl+/; FlitKey does not ship TE’s Chrome AI recommendations.

Can I use all three in FlitKey?

On Windows and Linux X11, yes. On Wayland, use the picker (and paste).

Sources and verification notes

Verified August 26, 2026.

• TextExpander Inline Search: Picker docs and default hotkeys.
• TextExpander keyboard shortcuts: Built-in vs customizable hotkeys.
• TextExpander 2025 recap: #1 request “find Snippets faster”.
• Abbreviation prefixes experts use: Trigger naming vs Inline Search.
• TextExpander best practices: Group prefixes + search.
• TypeFire: shortcuts vs abbreviations vs launcher: Independent 5–15 / 20–40 / long-tail mix.
• Zapier text expander guide: Inline search pattern.
• TextExpander pricing: Pro $60/yr, Business $120/yr.
• FlitKey docs: Keyword, hotkey, Alt+Space, Wayland.