TextExpander Does One Thing Better Than Me. Use Both.
I'm going to start this post by recommending a competitor. Not a "they're fine, I guess" recommendation, a real one. If you type the same exact words over and over, the exact same way, every single time, you should buy TextExpander, and you should use it alongside my app, because it does one thing better than WriteAmp ever will.
This isn't false modesty. It's the honest shape of the problem, and the people who understand the difference between the two tools are the ones who end up happiest with both.
The two kinds of repetition
Here's the thing nobody tells you about the sentences you type on repeat. There are two kinds, and they look the same until you look closely.
The first kind is boilerplate. The exact same words, every time, byte for byte. Your address block. Your standard non-disclosure paragraph. The "thanks for your order, here's what happens next" message that hasn't changed in three years. These want to be identical, because they're not really communication, they're machinery, and machinery shouldn't drift.
The second kind is near-repeat. The same shape, but different every time. "Thanks for the quick turnaround" becomes "thanks for sending that over" becomes "thanks for the update." The follow-up email that starts the same way but has a different date and a different ask. These aren't boilerplate. They're sentences you're actually writing, just in a familiar shape.
- Type a short abbreviation, get the exact full text
- Perfect for addresses, standard paragraphs, legal boilerplate
- A near-repeat would need a new snippet every time
- Finishes the sentence based on how you actually write
- Handles the variations without you maintaining anything
- Wouldn't be my first pick for your address block
Why the difference matters
The distinction matters because each tool is genuinely bad at the other's job, and I think most of the disappointment with both comes from using them wrong.
TextExpander is bad at near-repeats because a snippet is fixed. If you make one for "thanks for the quick turnaround," it expands to exactly that, every time, and when the situation calls for "thanks for sending that over," the snippet is useless unless you made a second one, and a third for the next variation. Before long you have a snippet library that's really a graveyard of every sentence you've ever typed, which is the opposite of what you wanted. Boilerplate wants to be managed. Near-repeats don't.
Autocomplete is bad at boilerplate for the opposite reason. It predicts, which means it can drift. If you rely on WriteAmp to produce your standard legal paragraph, you're trusting a model to reproduce it exactly, and that's the wrong tool for a job that demands zero variance. For text that has to be byte-identical, you don't want a prediction. You want a promise, and that's what a snippet expander gives you.
The honest version of this is that the tools are complements, and the best setup is both. I've recommended this to people who wrote to me annoyed that WriteAmp wouldn't reliably reproduce their boilerplate. The answer wasn't a better autocomplete. It was TextExpander, doing the job it was built for, next to WriteAmp doing the job it was built for.
WriteAmp and a snippet expander can live side by side without fighting. They both watch what you type, but they trigger differently, TextExpander on your abbreviations, WriteAmp on the natural flow of your sentence, so they rarely step on each other. Run both for a week and see which sentences each one catches.
How to split the work
Here's the practical split I use, and it's held up for a long time now.
The test for which bucket a sentence falls into is simple. Ask yourself: would it be wrong if one word changed? If yes, it's boilerplate, use the expander. If no, it's a near-repeat, and that's where autocomplete earns its keep by learning how you actually phrase things instead of making you maintain a library of every variation.
The honest close
I make the sentence-finishing tool, so it'd be easy to tell you that autocomplete replaces everything else. It doesn't. TextExpander is a good product that does a job WriteAmp is deliberately not built for, and the people who need that job should buy it, no guilt, no fine print. The category map has the fuller landscape if you want to see where everything fits.
And if the sentences you type are the near-repeat kind, the ones that vary just enough that a snippet library would be a graveyard, that's the job WriteAmp is built for, and the trial is free for 30 days if you want to feel the difference. The two tools aren't competitors. They're the two halves of the repetition problem, and now you know which half is which.
Sources
- WriteAmp compare page: the full WriteAmp vs. TextExpander framing, including where WriteAmp loses
On macOS 26+ Macs, Apple Intelligence mode stays free even after the trial ends — you always keep a working path to suggestions.
Written by Amit Ashwini, who builds WriteAmp and runs its marketing. More: why the Tab key beats the chat box · mini, midi, and max compared · benchmark methodology.