natkr/flickboard
7
64
Fork
You've already forked flickboard
16

Dynamic haptic feedback vibration to help with touch typing #402

Open
opened 2026年01月10日 16:17:38 +01:00 by Anarchtism · 0 comments

Context

I wonder if making haptic feedback vibration strongest when you tap or start a gesture in the center of a key and softer if you start further away from the center would help with touch typing.

Describe your suggested feature

When initially touching any key (to tap, long press, circle, U-swipe, or whatever), FlickBoard could vibrate differently based on where in each key it's being touched.

Other details

Nat on Discord, December 21st, 2024

hm... the "problem" here is that currently we don't define the vibe patterns, your device mfg/google does
and fb just says "hey the user tapped a key"
we could take control over that and switch to the raw vibe pattern API but
more complexity, more tuneables

Acknowledgements

  • I have searched the existing issues and this is a new one, NOT a duplicate or related to another open issue.
  • This is a single feature request, in case of multiple feature requests I will open a separate issue for each one (they can always link to each other if related)
  • I have written a short but informative title.
  • I have checked through the app settings for my feature.
  • I will fill out all of the requested information in this form.
### Context I wonder if making haptic feedback vibration strongest when you tap or start a gesture in the center of a key and softer if you start further away from the center would help with touch typing. ### Describe your suggested feature When initially touching any key (to tap, long press, circle, U-swipe, or whatever), FlickBoard could vibrate differently based on where in each key it's being touched. ### Other details **Nat on Discord, December 21st, 2024** > hm... the "problem" here is that currently we don't define the vibe patterns, your device mfg/google does > and fb just says "hey the user tapped a key" > we could take control over that and switch to the raw vibe pattern API but > more complexity, more tuneables ### Acknowledgements - [x] I have searched the existing issues and this is a new one, **NOT** a duplicate or related to another open issue. - [x] This is a **single** feature request, in case of multiple feature requests I will open a separate issue for each one (they can always link to each other if related) - [x] I have written a short but informative title. - [x] I have checked through the app settings for my feature. - [x] I will fill out all of the requested information in this form.
Sign in to join this conversation.
No Branch/Tag specified
main
spike/old/layout-editor-v1
spike/hct-colour-sliders
features/binary-landscape-keyboard-alignment
v0.3.4.1
v0.3.4
v0.3.4-beta1
v0.3.3
v0.3.3-beta1
v0.3.2
v0.3.2-beta2
v0.3.2-beta1
v0.3.1
v0.3.1-beta2
v0.3.1-beta1
v0.3.0.1
v0.3.0
v0.2.7
v0.2.7-beta7
v0.2.7-beta6
v0.2.7-beta5
v0.2.7-beta4
v0.2.7-beta3
v0.2.7-beta2
v0.2.7-beta1
v0.2.6.1
v0.2.6
v0.2.6-beta1
v0.2.5
v0.2.5-beta5
v0.2.5-beta4
v0.2.5-beta3
v0.2.5-beta2
v0.2.5-beta1
v0.2.4
v0.2.4-beta2
v0.2.4-beta1
v0.2.3
v0.2.2
v0.2.2-beta11
v0.2.2-beta10
v0.2.2-beta9
v0.2.2-beta8
v0.2.2-beta7
v0.2.2-beta6
v0.2.2-beta5
v0.2.2-beta4
v0.2.2-beta3
v0.2.2-beta1
v0.2.1
v0.2.1-beta9
v0.2.1-beta8
v0.2.1-beta7
v0.2.1-beta6
v0.2.1-beta5
v0.2.1-beta4
v0.2.1-beta3
v0.2.1-beta2
v0.2.1-beta1
v0.2.0.1
v0.2.0
v0.2.0-beta5
v0.2.0-beta4
v0.2.0-beta3
v0.2.0-beta2
v0.2.0-beta1
v0.1.11
v0.1.11-beta2
v0.1.11-beta1
v0.1.10
v0.1.10-beta1
v0.1.9
v0.1.8
v0.1.8-beta11
v0.1.8-beta10
v0.1.8-beta9
v0.1.8-beta8
v0.1.8-beta7
v0.1.8-beta6
v0.1.8-beta5
v0.1.8-beta4
v0.1.8-beta3
v0.1.8-beta2
v0.1.8-beta1
v0.1.7
v0.1.7-beta2
v0.1.7-beta1
v0.1.6
v0.1.6-beta7
v0.1.6-beta6
v0.1.6-beta5
v0.1.6-beta4
v0.1.6-beta3
v0.1.6-beta2
v0.1.6-beta1
v0.1.5
v0.1.4
v0.1.3
v0.1.2
v0.1.1
v0.1.0
v0.0.13
v0.0.12
v0.0.11
v0.0.10
v0.0.9
v0.0.8
v0.0.7
v0.0.6
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels
bug
Something isn't working
bug/gesture
A gesture recognition problem
bug/motorola
Bugs that have only been confirmed on Motorola devices
bug/samsung
Bugs that have only been confirmed on Samsung devices
bug/unreproducible
A bug that I can't seem to reproduce, more information is required
cleanup
Maintenance tasks
community
Community/discussion infrastructure
design
Involves design question(s)
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
emoji
Emoji-related features
feature
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
invalid
This doesn't seem right
layout
Add or change a keyboard layout
meta
Questions about the process itself
question
Further information is requested
wontfix
This will not be worked on
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
natkr/flickboard#402
Reference in a new issue
natkr/flickboard
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?