Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option for Sound / Haptic feedback #374

Open
2 tasks done
Clozent opened this issue Oct 23, 2023 · 1 comment
Open
2 tasks done

Option for Sound / Haptic feedback #374

Clozent opened this issue Oct 23, 2023 · 1 comment
Labels
feature New feature or request help wanted Extra attention is needed

Comments

@Clozent
Copy link

Clozent commented Oct 23, 2023

Terms

Description

A really nice feature the default iOS keyboard is the sound feedback of typing, making it clear when a key is registered.
While haptic feedback does not seem to exist in the default iOS keyboard, it is also a great feature to add, making each tap really satisfying.

It is important to add that I think these features need to be separately tunable, since some people may find one or both of these features annoying or too strong / soft.

Contribution

No response

@Clozent Clozent added the feature New feature or request label Oct 23, 2023
@andrewtavis andrewtavis added the help wanted Extra attention is needed label Oct 23, 2023
@andrewtavis
Copy link
Member

Hey @Clozent! Thanks for opening the issue :) :) It's definitely something for later, and we'll for sure keep this issue open and see how the interest in it develops. As of now we want to make sure that we're not asking for any user data whatsoever as we're still in the early stages. In order for sounds to be played, Scribe would need to ask the user for access to their microphone when they try to activate a keyboard, and if memory serves me the wording in the system UI isn't very good such that people might worry that we're accessing more than they'd be comfortable with us having.

I'd say that haptic feedback would be of lower priority as it's not expected at all. Both would as you say need menu options and be off by default as maybe that would allow us to not need to directly ask for device access on activating the keyboard, but only when they turn them on in Scribe's settings.

Definitely something to keep our eye on though! Again, appreciate you bringing this up 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request help wanted Extra attention is needed
Projects
Status: Todo
Development

No branches or pull requests

2 participants