Follow-up to #350 (discussion), where a user reported a dictation "stuck in Transcribing".
The wait is often longer than it looks. A retryable failure is retried three times three seconds
apart, so a provider on its 120 s budget can take around eight minutes before an error finally
appears — and for all of that the Smartbar says only Transcribing…, unchanged, with a spinner that
looks the same at second two and at minute seven. There is no way to tell a slow answer from a dead
one, which is exactly what the report describes.
The recording state already solves this: it shows an elapsed m:ss timer next to the dot. The
transcribing state should say the same thing.
What to build: append the elapsed seconds after Transcribing…, as 12 s, in a smaller font
than the status text and vertically centred against it.
- The clock starts when the state first becomes
Transcribing and survives a retry and the
on-device fallback — those replace the state object, but they are the same wait as far as the
person watching is concerned, and the total is the number that answers their question.
- Reuses the existing non-translatable
unit__seconds__symbol ({v} s), so no new strings.
- Same treatment in the legacy (keyboard-less) layout, which shows the same status.
Follow-up to #350 (discussion), where a user reported a dictation "stuck in Transcribing".
The wait is often longer than it looks. A retryable failure is retried three times three seconds
apart, so a provider on its 120 s budget can take around eight minutes before an error finally
appears — and for all of that the Smartbar says only
Transcribing…, unchanged, with a spinner thatlooks the same at second two and at minute seven. There is no way to tell a slow answer from a dead
one, which is exactly what the report describes.
The recording state already solves this: it shows an elapsed
m:sstimer next to the dot. Thetranscribing state should say the same thing.
What to build: append the elapsed seconds after
Transcribing…, as12 s, in a smaller fontthan the status text and vertically centred against it.
Transcribingand survives a retry and theon-device fallback — those replace the state object, but they are the same wait as far as the
person watching is concerned, and the total is the number that answers their question.
unit__seconds__symbol({v} s), so no new strings.