mjhjmtu

I am designing an app for iOS where I need to prevent user to unintentionally trigger an alarm (the action of calling for emergency should be easily accessible but at the same time should prevent any accidental initiation).

I don't want to use confirm dialog since it requires user to read and looking for a button in different position. (seems like too much friction on the other side)

What occurred to me initially as an good idea was to use 'slide to' action button, similar to what was/is used to unlock iPhone screen, but then I run to this topic: https://stackoverflow.com/questions/40500955/creating-a-slide-to-power-off-like-slider-on-ios
basically saying that Apple discourage usage of these kinds of components refuse to publish such an app in the store.

Do you have any experience with this kind of user scenarios?
Or do you have experience with apple refusing to publish your app for such reasons?

Thanks!

Additional ideas from this article:
https://www.smashingmagazine.com/2018/01/friction-ux-design-tool/

1. Delaying the action and allow a window time for users to "undo"


2. Extra step for security, such as asking for fingerprint


3. Other types of authentication such as re asking password or 2-factor authentication.

Other articles dealing with the same topic:

• https://uxdesign.cc/friction-as-a-function-in-user-experience-make-me-think-390ee17c6cf5


• https://uxplanet.org/when-friction-in-design-is-good-for-ux-e2dd82cfab67

First, regarding answer that you linked, I think what Apple was having an issue with is the use of the same UI as their slide to power off, not the use of that UX/interaction. They just don't want it to be styled to resemble their power off slider as to not confuse users. If you were to create say, a small blue slider, or a slider that moves in a circle pattern I think you'd be fine.

However, if you want to play it safe, what about press to hold like this:

Screen recording from MapMyRun app

In the .gif, a user is pressing the "hold to finish" button, which triggers a roughly 2 seconds "finshing" state where a user can let go and cancel the action, or after two seconds the action, in this case "finshing", triggers. There is a visual progress indicator to show the user that they are performing the action and how long until the action completes. You could also experiment with increasing the time or providing haptic or audible feedback to prevent false presses. This also meets your need of not having to read or click anywhere else.