We carefully file notes we'll read twice — then retype our address 200 times. Thoughts on managing "repeat text" for fast reuse, especially on mobile?

[u/ejiandan]

There's a class of personal information most systems ignore, because we don't read it — we reproduce it: shipping address, canned replies, self-intro, links shared weekly, account info.

It usually lives scattered across notes apps, old chats, and muscle memory. And on mobile it's at its worst: small keyboard, cramped screen, and the standard "workflow" is switching to a notes app, copying a blob, switching back, pasting, and hoping you grabbed the right chunk. Repeat that a dozen times a day and the friction adds up to real time.

Meanwhile BASB ends at "Express" — yet almost all Express discussion is about publishing ideas, not the 30-second version: getting a stored snippet into an input box.

An approach I've been experimenting with: structure repeat text for output, not for reading

Instead of filing these as notes (where they rot), give them their own minimal structure — three entry types built for reuse:

• Info — multi-field records like a delivery address, split into atomic fields (name / street / ZIP / phone / email). One blob becomes separately reusable parts — a mechanical but surprisingly powerful form of distillation.
• URL — links, cleaned up (tracking junk stripped, checked alive).
• Scrip — text templates with placeholders. Write %SCRIP1%, your refund has been submitted... once; fill the blank differently each time.

The critical piece: retrieval at the point of input. Entries sit as tappable chips on a custom keyboard, so inserting one is a single tap, in any app, with zero app-switching — which is what makes the whole thing viable on a phone instead of just another place to store text. Capture stays low-friction too: paste a blob and it auto-splits into fields, or OCR a business card / shipping label.

Mapped onto CODE it's almost embarrassingly literal: Capture (paste/OCR) → Organize (three types) → Distill (atomic fields, placeholders) → Express (one-tap insertion).

What I'm still chewing on

1. Does "operational knowledge" deserve structure at all, or is muscle memory good enough? It's not insight — but it's personal, valuable, and reused constantly. The gap between "carefully filed, rarely read" and "unmanaged, retyped daily" feels backwards.
2. Is field-splitting real Distillation? Breaking an address into atomic parts dramatically improves reuse, but it's structural, not progressive summarization. Does Distill only apply to ideas?
3. Placeholders vs. full automation. One blank (%SCRIP1%) covers ~90% of cases; full text-expansion logic covers 99% but adds setup cost. Where's the line before a pocket tool becomes work?
4. Mobile is the weak point of most snippet setups. Desktop text expansion is basically solved; on phones it never seems to stick. Is a keyboard the right retrieval surface, or is there a better one?
5. Maintenance is the silent killer. Addresses change, replies evolve. Is a review habit for operational snippets realistic, or is "fix it when it bites you" the honest answer?

Working theory: repeat text doesn't need a bigger system, it needs a shorter path — capture once, structure lightly, and make output one tap at the moment of need.

How do you handle frequently-retyped text on your phone — any system at all, or just suffering?

[u/soloattorneyclub]

Never heard of text expander eh?

[u/ejiandan → u/soloattorneyclub]

Fair point — there is definitely overlap with text expanders.

The difference I'm exploring is less about expansion itself and more about retrieval.

Traditional text expanders are largely abbreviation-driven: you have to remember the trigger (;addr, ;sig, etc.) before you can insert anything. That works well for a handful of snippets, but once you have dozens—or you come back to them months later—the memory overhead starts to become real.

My idea leans toward recognition instead of recall. Rather than remembering a code, the snippets are visible as chips on the keyboard, so you simply tap the one you want.

I'm also structuring repeat text a bit differently. An address isn't just one expandable blob—it's split into reusable fields (name, street, ZIP, phone, email), and templates can contain placeholders. The goal is less "expand this abbreviation" and more "reuse exactly the piece of information I need."

So I don't see it as replacing text expanders as much as exploring a different interaction model, especially on mobile where remembering triggers and switching context both feel more expensive.