Haptics

[jcesarmobile]

Android implementation has been reworked based on https://github.com/expo/expo/tree/master/packages/expo-haptics

see ionic-team/capacitor-testapp#7 and ionic-team/capacitor#3363

[cameronrr]

Thanks for all the work on this. Two points for discussion below:

Message for'API Not Available'
In the Share plugin, a false feature detection returns 'Web Share API not available'. Is it worth having a consistent messaging from Capacitor plugins in this scenario i.e. if Haptics is not available, to output 'Web Haptics API not available' instead of 'Vibrate API not available in this browser'. Specificity could follow the standard message if needed i.e. 'Web Haptics API not available - not supported by this browser'. There might be value in a consistent format not only for clearer plugin development but for developers to quickly recognise the pattern and that it is from the Capacitor web plugin.

Vibrate Options
The Web API supports not only a number as the duration parameter, but also an array (Number[]) to define a vibration pattern. Is it possible to handle this in the web plugin to leverage the full set of Vibrate API features? I think the main consideration is the interaction with native plugins if the options/capabilities are different. I think the goal is a single interface for developers regardless of device so not sure how this would be approached.

[imhoffd]

@cameronrr Good input, thanks! I agree, we need to be consistent about error messages. I hope to have a code associated with each error so you can just check if (e.code === 'ERR_WEB_API_UNAVAILABLE") for example. As for the vibrate options, I'm not sure it's in the scope of this plugin. We want people to use the high-level haptics methods. We've debated removing the vibrate() method completely. I think there's room for an "advanced vibration" plugin in the Capacitor community (and keep in mind, iOS doesn't support patterns or even different length vibrations).

[nicolocarpignoli]

Hi everybody.
It seems that from iOS 13+ it is possible to use CoreHaptics API on iOS and handle more fine grained haptics feedbacks.
For example, we can manage the duration https://developer.apple.com/documentation/corehaptics/chhapticevent/3081790-duration?language=objc.

Does this PR introduced such behaviour, or it is not based on CoreHaptics?

Thank you