Typed Triggers vs Hotkeys vs Pickers (2026): Pick a Mix

The decision is retrieval, not features

Text expanders fail in the head more often than in the engine: you have the refund paragraph, but you cannot remember whether it was ;ref2 or ;refund.

TextExpander’s 2025 product recap named the top user request, by far: “Help me find Snippets faster” (community post, Dec 2025, checked 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 ways to retrieve the same snippet. Choose by how often you use it and how often you forget it, 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, checked August 2026). That mix stays useful 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 and then replaces.

You stay in the sentence with no modal and no mouse, which is why people start here and why it still wins for muscle-memory strings like ;em, :addr, and //te.

Costs: You have to remember the string, and 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 (typed keywords are not supported inline), and apps that swallow synthetic keys (see the compatibility guide).

Hotkeys: instant, and you will run out

A hotkey is a chord, and two jobs often get mixed together:

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, checked August 2026).

Snippet hotkeys win 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; five is easy, fifteen is ambitious if you stay 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), and 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 so you never spend a minute reconstructing a template you already wrote. Labels matter more than clever triggers here; 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, and the snippet copies to the clipboard for paste. That same path is the compatibility escape hatch when typed inject fails.

How FlitKey maps onto the three

Treat this as a capability gate, not a brochure.

• Windows / Linux X11: typed keyword, per-snippet hotkey, and Alt+Space Quick Insert are all available.
• Linux Wayland: picker via app/tray + clipboard paste only. Typed triggers and snippet hotkeys are off in v0.6.0.

From the published compatibility CSV, Gedit, Chrome, VS Code, and GNOME Terminal are PASS for typed expand on Ubuntu X11 and PARTIAL on Wayland (GNOME 46) with Quick Insert + paste. Practice with the YAML fixture before you commit a method. If your daily driver is a Wayland session, skip the keyword debate and train the picker first; full notes are in the Wayland guide.

Gaps worth stating plainly: no TextExpander-style Inline Search AI, no Espanso regex/word: true, no macOS build. What you get is a visual mix on Windows/Linux without YAML or a per-seat sync bill.

A working mix (not a purity test)

Linux users on X11: typed + picker is usually enough; add a couple of hotkeys only if those chords already live in your fingers.
Linux users on Wayland: skip the keyword debate and learn the picker first.
Windows: you can use all three, but still cap the hotkey list.
Teams on Mac + mobile: TextExpander’s Inline Search + shared groups still win at the org layer.

Hands-on: one snippet, three activations

Use the same body for all three:

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

Trigger (FlitKey keyword)

keyword: :fup
Type :fup in the ticket; it expands in place on Windows/X11.

Hotkey

trigger_type: hotkey, with a chord you will actually remember.
Press it with the ticket ID already copied so no abbreviation shows up in the transcript.

Picker

Alt+Space, then search follow or report. On Wayland, paste from the clipboard.

Create the keyword first and bind Alt+Space the same day. Add a hotkey only after you catch 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 typing that string. FlitKey supports both on a per-snippet basis.

Should I assign a hotkey to every snippet?

No. Chords collide with OS and app shortcuts, and you will forget most of them. Cap snippet hotkeys and put the rest on prefixes plus the picker.

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

Use the picker when you cannot remember the abbreviation, the library is large, typed expansion is blocked (some apps, or FlitKey on Wayland), or the snippet is rare enough that a dedicated trigger is wasted effort.

Does FlitKey include a picker like TextExpander Inline Search?

Yes: Quick Insert (Alt+Space on Windows/X11) does the 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

Checked 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.