New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 677668 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Feature



Sign in to add a comment

Haptic/audio feedback API

Reported by nekr.fab...@gmail.com, Dec 30 2016

Issue description

Steps to reproduce the problem:
1. Open typical native
2. Tap on something clickable
3. Audio or haptic feedback happens (depending on phone settings, enabled sounds, etc)

4. Open PWA added to Home Screen by Chrome
5. Tap something clickable in the app
6. No feedback

What is the expected behavior?
PWA should probably behave as native apps here and have haptic/audio feedback on taps. 

This probably makes sense only for WebAPK.

What went wrong?
Web pages in browsers do not have haptic/audio feedback right (it used to have in older version of Android browser?) and PWAs inherited this behavior.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version:   Channel: n/a
OS Version: 
Flash Version: 

Cordova developers use "feedback plugin" for that and call it manually on click in their apps. Existence of such plugins proves and it's at least usable for developers and probably is also usable for their users.
 
Cc: tedc...@chromium.org
Owner: dfalcant...@chromium.org
Status: Assigned (was: Unconfirmed)
Cc: -tedc...@chromium.org dominickn@chromium.org pkotw...@chromium.org hanxi@chromium.org dfalcant...@chromium.org sbirch@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
Not sure how to triage this one.  Paging webapp Super Friends.
Cc: slightlyoff@chromium.org owe...@chromium.org
+cc owencm, slightlyoff
Components: UI>Input>Touch Mobile>WebAPKs
Owner: owe...@chromium.org
Status: Assigned (was: Untriaged)
Seems like an ambitious feature request. Assigning to Owen for a clear concise decision

Comment 7 by owe...@chromium.org, Feb 16 2018

Components: -Mobile>WebAPKs
Labels: -Type-Bug -Via-Wizard-API Type-Feature
Summary: Haptic/audio feedback API (was: Support of haptic/audio feedback in PWAs on Android)
I'll own this feature request.

I've talked with a few folk about a haptic or audio feedback API in the past, I have it on a conceptual long term backlog (although of course we may never get to it, or decide against for some reason).

No other action required from folk here. 

If anyone wants to see this happen particularly, feel free to star this so I can get a general sense.

(also I don't think this would be WebAPK specific, so removing webapk labels and -cc webapk folk)

Comment 8 by owe...@chromium.org, Feb 16 2018

Cc: -dominickn@chromium.org -owe...@chromium.org -pkotw...@chromium.org -sbirch@chromium.org -dfalcant...@chromium.org ojan@chromium.org
Labels: -Pri-2 Pri-3
cc ojan who I've discussed this with in the past. Relevant from autoplay audio policy etc.

Comment 9 by ojan@chromium.org, Feb 17 2018

Cc: mlamouri@chromium.org
Audio feedback on click should be compatible with the autoplay policy and one could use Web Audio for this.

Couldn't haptic feedback be done with the Vibration API? I mean, is this different from a small vibration or is this a different motor that would require its own API or an extension to the Vibration API?
Audio element/web audio plays through "speakers", aka Sound. Tap audio
feedback plays through Phone audio. That's different audio settings on a
phone. Also while audio feedback might be enabled, haptic feedback may be
disabled (and vice versa, or both disabled) in the settings and web app
wouldn't know about it.
Thanks for the background. I guess I would need to do more research on this. Though, with regards to the question asked in comment #8, there is no problem with the autoplay policy as it would happen on a user gesture.

Comment 13 by ojan@chromium.org, May 8 2018

Cc: -ojan@chromium.org

Sign in to add a comment