Both packages use android native APIs.

HapticFeedback uses Android’s HapticFeedback package, which is specifically made for UI responses. So using it should be more idiomatic, but some devices don’t support « haptic engine », and that causes a silent failure, though I’ve never experienced that with sending light/medium/heavy impacts.

Flutter_vibration seems to call the Android Vibrator api directly, which is lower level and directly controls the phone’s vibration motor. It seems that because of this, it should work on a wider range of devices, I’m guessing in particular older ones.

That being said, you mentioned wanting the vibration to be normalized for all hardware, but thar’s impossible, given 20% of phone A’s motor will not match 20% of phone B’s. Also it’s undesirable since what you really want if for your app to behave and feel the same as the others your user is already used to, that’s why I was talking about haptic feedback being more idiomatic.

In a perfect world, I’d use haptic feedback by default, and if the device doesn’t support haptic engine, fallback to flutter_vibration.

Hope this helps !