Haptic feedback only on touch-down event?

[chrisballinger]

I'm curious if you've tried only doing the feedback on touch-down only, and not on touch-up.

If I touch the key fast enough I only seem to get the touch-down feedback, which makes the response feel inconsistent sometimes. Then I started wondering what it felt like if was possible to only send one haptic event instead of two.

[niw]

It is using both touch down and up and triggers different type of haptic feedbacks, as long as these two events are not happening in a very short period, which is 50ms now.
This is intentional implementation to address #3.

I think it’s reasonable behavior, however this is fixed value so we may want to adjust or make it configurable.

[munsuri]

For quick taps, personally, I find one key stroke (down) more natural with a better feeling. I have added three more cases to the app such as Down/Up key event (default), Down Key event or Up key event to keep experimenting.

[muescha]

@munsuri can you create also a pull request for your changes?

[JMY1000]

It'd be nice to have this be configurable, as I'd prefer a much longer time. Asking the user to rebuild seems like kinda a hassle. I'd love to contribute, but Objective-C is unfortunately outside my wheelhouse for now.

[DennisSchiefer]

I played around with the kMinimumActuationInterval a bit and found that 200ms gives a pretty good experience for me personally.
Anything longer, I experience as a proper key press that should have down and up feedback.
Anything shorter, I experience as a tap, for which a single feedback is sufficient.

Also, major thumbs up to @niw for making this easy to compile (without any Ruby or XCode experience)!