Skip to content

A physical therapist's instruction was specific: no more than twenty minutes of continuous typing a day for the next month, with breaks in between. That leaves most of a workday's writing needing another way to get done. This is one version of what that day looks like, built around a toggle instead of a keyboard, with the twenty-minute budget spent on the handful of things that genuinely need a keyboard and nothing else.

9:15 AM — starting with the mode that doesn't ask for a sustained hold

Holding ⌥ Space is the default way to dictate, but a toggle is also available — one tap starts a dictation, a second tap ends it, so no key needs to stay pressed for the length of a sentence. For a hand still easing back into typing at all, the difference between a sustained hold and two short taps is worth choosing deliberately rather than defaulting to whichever mode came first.

⌥ Space→ Mail5.3s

Following up on yesterday's thread — happy to join the call, but I'll need the agenda sent ahead of time this week.

A full email reply, started and stopped with two taps rather than one held key.

10:40 AM — a long Slack thread, said instead of typed in short bursts

The instinct with hand pain is often to type in short bursts and rest between them, which still adds up to a meaningful amount of keystrokes across a morning. Saying the same reply instead removes that volume entirely for whatever gets dictated, leaving the twenty-minute budget untouched for later.

⌥ Space→ Slack6.7s

The staging deploy looks good on my end — I checked the three flows we flagged yesterday and nothing regressed. Ready to ship whenever the team is.

A reply that would have been several short typing bursts, said once in the toggle mode instead.

11:45 AM — a break, taken without losing a half-said sentence

The therapist's plan calls for a short break every hour regardless of how the morning is going, and the habit that makes that easy to actually follow is not needing to finish a thought before stepping away from the desk. A sentence dictated moments before the break is already sitting in local history the instant the key is released — there's nothing half-typed left open on the screen to come back to, and nothing lost by getting up exactly when the timer says to rather than finishing "just this one line" first.

1:30 PM — the twenty minutes that still need a keyboard

Not everything moves to voice. A spreadsheet formula, a password field, and a quick rename in Finder still need actual keystrokes, and today's budget is spent here — deliberately, on the tasks dictation genuinely cannot do, rather than on the email and chat replies that could just as easily be said.

3:00 PM — a status update, held instead of toggled, by choice

Not every dictation uses the toggle. A short, one-line update is sometimes easier said with a quick hold-and-release than with two separate taps, and switching between the two modes across a day, based on what a given moment actually calls for, is itself part of building a habit that doesn't strain in one direction all day.

⌥ Space→ Notes3.9s

Ready for review — left comments on the two open questions, everything else looks fine to merge.

A short update dictated with a quick hold, chosen over the toggle for a sentence this brief.

4:15 PM — comparing the hold and the toggle at the end of the day

By late afternoon, the two modes have earned different reputations for this particular day. The toggle removed the sustained hold for the longer replies, at the cost of two deliberate taps instead of one — a fine trade for a five-sentence Slack thread and an odd one for a two-word confirmation. The held key stayed the better fit for the handful of short, one-line updates, where a quick press-and-release is less motion than tapping twice. Neither mode is the correct one in general; which fits a given sentence turns out to depend more on the sentence's length than anything else, and noticing that across a real day is worth more than picking one mode and defaulting to it for everything.

What the day's history shows, end to end

History3 of them, on your Mac
  • 09:165.3sFollowing up on yesterday's thread — happy to join the call, but I'll need the agenda sent ahead of time this week.Mail
  • 10:416.7sThe staging deploy looks good on my end — I checked the three flows we flagged yesterday and nothing regressed.Slack
  • 15:013.9sReady for review — left comments on the two open questions, everything else looks fine to merge.Notes
Three dictations across a day built around a twenty-minute typing budget — none of them touched that budget.

The count that actually matters for a day like this isn't how fast any one sentence went in — it's how much of the day's total writing avoided the keyboard altogether, leaving the budget for the handful of tasks that genuinely needed it.

What a held key or a toggle does not do

Either mode only types text into whatever field is focused. It doesn't click, scroll, or navigate — the mouse and trackpad work exactly the way they did before. For someone whose pain comes from clicking and scrolling as much as from typing, Talon and macOS Voice Control cover the parts of a workday this app leaves untouched, and the fuller comparison of accessibility tools covers both categories honestly rather than implying a dictation hotkey closes a gap it doesn't.

Typing is only one axis of a workday, and for anyone whose limit extends past the keyboard to the mouse and trackpad as well, the page on accessibility typing on a Mac covers the same hotkey from that broader angle.

Why the twenty minutes matters more than the total word count

It would be easy to measure a day like this one by how many words got said instead of typed, but that number misses the actual point of the budget. A therapist's instruction about continuous typing is about the strain of sustained, repetitive keystrokes, not about total output — dictating a thousand words changes nothing about the twenty minutes of typing still required for the spreadsheet, the password field, and the Finder rename, and it was never meant to. The honest way to think about a day like this one is not "how much did I avoid typing" but "did the twenty minutes that remained stay within the limit, without quietly stretching past it because a task felt faster to just type through." Those are different questions, and only the second one is the one the therapist actually asked.

Setting up the toggle without adding new friction

Switching from the default hold to a toggle, or back again mid-day, is a setting rather than a separate install, and it's worth confirming the chosen hotkey doesn't collide with anything else already bound to ⌥ Space in System Settings before relying on it for a full day — the walkthrough for setting up the hotkey covers both modes and the conflict check in more detail than a single day's account can.

Why a stalled app matters more on a day like this one

  1. 1Key downthe target is chosen here
  2. 2You speaklevel meter, over your work
  3. 3Key up
  4. 4Written to historybefore the engine is asked
  5. 5Engineon your Mac
  6. 6Typedabout half a second
The words are written to history before the engine is asked anything — a stalled app on a day with a strict typing budget costs a copy-and-paste, not a retyped sentence.

Retyping a paragraph that shouldn't have needed typing once already is a worse outcome on a day with a fixed budget than on an ordinary one — every retyped word is one taken directly out of the twenty minutes set aside for what actually needs a keyboard. Because each dictation is written to local history the instant the key is released, before the engine is asked to produce anything, a stalled window or a paste that doesn't land costs a copy-and-paste from history, never a second round of typing.

Bringing the log to a weekly check-in

The therapist asked, at the first appointment, roughly how much typing a day's work actually required — a question that's hard to answer honestly from memory alone. Local history answers it more concretely than a guess would: scrolling back through a week's rows shows, plainly, how much of a day's writing ended up dictated rather than typed, and on which days the twenty-minute budget actually held. It isn't a report generated for the appointment and nothing here tallies the totals automatically — it's just a timestamped list, on the machine it was made on, that happens to be honest in a way an end-of-week recollection often isn't. Bringing it up on a laptop during a check-in turned out to be a better way of answering "how much are you actually typing" than trying to reconstruct the week from memory in the waiting room.

The chair, the desk and the keyboard haven't gone anywhere

None of this replaced the ergonomic changes already in place before the budget started — the keyboard tray, the wrist rest, the monitor raised to eye height. A dictation hotkey changes how much of the day's writing needs the keyboard at all; it does nothing about the twenty minutes that still do, and the equipment recommended for that twenty minutes matters exactly as much as it did before any of this started. Treating a toggle as a replacement for an ergonomic setup, rather than a way of reducing how much that setup gets used, would be a mistake this page is written to head off rather than encourage.

What this does and does not claim

It does not diagnose anything, does not recommend a typing budget, and does not promise to reduce pain or speed up recovery. What it changed about this particular day was narrower and more specific: a fixed amount of writing moved from keystrokes to speech, freeing the day's actual typing budget for tasks that had no other way to get done. The broader page on what this means for RSI generally covers the same limits at more length, and reducing typing volume specifically walks through the mechanics this one day only shows in practice.

What it costs and what it needs

$19 once, three devices per licence, macOS 13 Ventura or later, Apple Silicon or Intel. The thirty-day trial runs the complete app, no card and no account — long enough to try both the hold and the toggle against a real week's actual writing and notice, honestly, how much of a typing budget it actually frees up, before spending anything on it.

Nothing here uploaded, on a day already asking a lot

None of the day's dictations — the email, the Slack reply, the short status update — were uploaded anywhere, on any tier, and the whole day would have run identically with the network off. That matters less for the mechanics of a typing budget than the rest of this page and is worth stating anyway: nothing about a day already built around a physical limit should also require trusting where the words go afterward.

What a habit built around a limit actually looks like after a month

A single day like this one proves very little on its own — the real test is whether the pattern holds once the novelty of a new toggle wears off and the old habit of just typing through a short reply starts to feel easier again. What made it hold, across the four weeks the therapist's instruction covered, was less about the app and more about noticing, in the moment, which of the day's tasks actually needed a keyboard and which ones only felt like they did out of habit. A short Slack reply typed out of reflex, before remembering there was another way to produce it, happened less often in the second week than the first, and less again by the fourth — not because the toggle got faster, but because the pause to ask "does this need typing" became automatic in a way it wasn't on day one.

What the log looked like by the end of the month

By the fourth week, the pattern in local history had shifted noticeably from the first: fewer short entries logged from the keyboard directly, more substantial ones dictated, and — the number that mattered most to the therapist — no week where the twenty-minute ceiling was quietly exceeded without noticing. None of that shift came from the app getting better at anything; the mechanism on day one and day thirty was identical. What changed was entirely the habit of reaching for a toggle before reaching for a keyboard, built one deliberate choice at a time across a month of otherwise ordinary workdays.

What next week changes, if anything

The honest measure of a week like this one isn't whether any single dictation felt faster than typing — it's whether the twenty-minute budget held, end to end, without being borrowed from to cover an email that could have been said instead. That's the only number worth reporting back to whoever set the budget in the first place, and it has nothing to do with how this app performed and everything to do with whether the day around it actually changed.

Questions

Does this workflow treat or improve RSI?
No. It describes how one person built a workday around a typing limit set by their own physical therapist. Whether reducing typing helps a specific case is a question for whoever is already treating it, never a comparison page.
Why does this workflow use a toggle instead of holding the key down?
A toggle starts and stops a dictation with two separate taps instead of one sustained hold, which some people recovering from hand strain prefer. It's an available mode, not a claim that holding a key is unsafe for anyone else.
Does switching to a toggle remove hand use entirely?
No. A key still gets pressed to start and stop each dictation — the toggle changes the motion from a sustained hold to two short taps, not to no motion at all.
Can this replace the exercises or breaks a therapist already recommended?
No. Nothing here substitutes for a treatment plan. It only changes how the typing that's still allowed gets done, and the pacing habits below are worth checking against whatever a therapist has already recommended.
What happens to a sentence if a break gets taken mid-dictation?
It's already written to local history the instant the key is released, before the transcription engine does anything with it, so stepping away mid-sentence costs nothing — the words are already saved.