App
Android app
Problem
This mentions a previous issue of mine, and I don't know if I should have made a comment to it instead of opening a new issue.
In 0.1.0-beta.14 the Start Dictation button combined two actions in itself: Start Dictation and "Stop Dictation -> Transcribe -> Insert the text".
I created a feature request suggesting to tie "Stop Transcribing -> Cancel Transcribing -> Do Not Insert the text" to a long tap on the Start/Stop Dictation button while Recodring is already going. So the button was kept the same, no new entities.
In 0.1.1 which I've installed yesterday I see the "X" button near alongside the Stop Dictation button which stops recognition without saving and inserting the result. I find this part of UI now a bit overloaded. It seems to me that it was redundant to create a whole new button for this purpose right near the existing one which just could be extended with a second interaction depth layer (long tap).
Now when I'm outside and walking, I'm afraid to miss the button and hit the X button without real intention because of constant movement each time. I suppose people use voice input exactly for while moving most of the time. In the meanwhile, long tap can be done only on purpose, with an explicit user intention.
I feel this novelty worsens the UX, makes it feel less reliable.
Smallest change
I'm still suggesting adding the feature exactly as a long tap instead of creating a new entity with a an easy Danger Action triggering (a whole message cancellation).
As for such a placement for this secondary action, which could clearly announce its existance to users, it could be articulated to users with a pictogram right inside the Start/Stop button while Recording:
or
(I don't really like these desings, just shared as a reference. A pretty+consise design for this turned out harder to think up than it seemed)
Or it just could be written somewhere, e.g. on First Setup onboarding screen or as a floting toast message a few times while first. Maybe it doesn't actually need a nint for users at all. It's pretty natural for users to try long tap on things. So when a user sees that a short tap makes everything transcribed, why not to try a long tap?
Other options (optional)
No response
Before you submit
App
Android app
Problem
This mentions a previous issue of mine, and I don't know if I should have made a comment to it instead of opening a new issue.
In 0.1.0-beta.14 the Start Dictation button combined two actions in itself: Start Dictation and "Stop Dictation -> Transcribe -> Insert the text".
I created a feature request suggesting to tie "Stop Transcribing -> Cancel Transcribing -> Do Not Insert the text" to a long tap on the Start/Stop Dictation button while Recodring is already going. So the button was kept the same, no new entities.
In 0.1.1 which I've installed yesterday I see the "X" button near alongside the Stop Dictation button which stops recognition without saving and inserting the result. I find this part of UI now a bit overloaded. It seems to me that it was redundant to create a whole new button for this purpose right near the existing one which just could be extended with a second interaction depth layer (long tap).
Now when I'm outside and walking, I'm afraid to miss the button and hit the X button without real intention because of constant movement each time. I suppose people use voice input exactly for while moving most of the time. In the meanwhile, long tap can be done only on purpose, with an explicit user intention.
I feel this novelty worsens the UX, makes it feel less reliable.
Smallest change
I'm still suggesting adding the feature exactly as a long tap instead of creating a new entity with a an easy Danger Action triggering (a whole message cancellation).
As for such a placement for this secondary action, which could clearly announce its existance to users, it could be articulated to users with a pictogram right inside the Start/Stop button while Recording:
or
(I don't really like these desings, just shared as a reference. A pretty+consise design for this turned out harder to think up than it seemed)
Or it just could be written somewhere, e.g. on First Setup onboarding screen or as a floting toast message a few times while first. Maybe it doesn't actually need a nint for users at all. It's pretty natural for users to try long tap on things. So when a user sees that a short tap makes everything transcribed, why not to try a long tap?
Other options (optional)
No response
Before you submit