How to design intentional friction in app?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
3
down vote

favorite












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!










share|improve this question







New contributor




enn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    up vote
    3
    down vote

    favorite












    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!










    share|improve this question







    New contributor




    enn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.





















      up vote
      3
      down vote

      favorite









      up vote
      3
      down vote

      favorite











      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!










      share|improve this question







      New contributor




      enn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      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!







      ios






      share|improve this question







      New contributor




      enn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      enn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      enn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 4 hours ago









      enn

      161




      161




      New contributor




      enn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      enn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      enn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          1
          down vote













          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





          share|improve this answer



























            up vote
            1
            down vote













            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:



            "press to hold"
            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.






            share|improve this answer




















              Your Answer








              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "102"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              convertImagesToLinks: false,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              noCode: true, onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );






              enn is a new contributor. Be nice, and check out our Code of Conduct.









               

              draft saved


              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fux.stackexchange.com%2fquestions%2f122057%2fhow-to-design-intentional-friction-in-app%23new-answer', 'question_page');

              );

              Post as a guest






























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              1
              down vote













              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





              share|improve this answer
























                up vote
                1
                down vote













                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





                share|improve this answer






















                  up vote
                  1
                  down vote










                  up vote
                  1
                  down vote









                  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





                  share|improve this answer












                  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






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 3 hours ago









                  Nicolas Hung

                  994410




                  994410






















                      up vote
                      1
                      down vote













                      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:



                      "press to hold"
                      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.






                      share|improve this answer
























                        up vote
                        1
                        down vote













                        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:



                        "press to hold"
                        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.






                        share|improve this answer






















                          up vote
                          1
                          down vote










                          up vote
                          1
                          down vote









                          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:



                          "press to hold"
                          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.






                          share|improve this answer












                          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:



                          "press to hold"
                          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.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered 3 hours ago









                          DasBeasto

                          12.5k54368




                          12.5k54368




















                              enn is a new contributor. Be nice, and check out our Code of Conduct.









                               

                              draft saved


                              draft discarded


















                              enn is a new contributor. Be nice, and check out our Code of Conduct.












                              enn is a new contributor. Be nice, and check out our Code of Conduct.











                              enn is a new contributor. Be nice, and check out our Code of Conduct.













                               


                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fux.stackexchange.com%2fquestions%2f122057%2fhow-to-design-intentional-friction-in-app%23new-answer', 'question_page');

                              );

                              Post as a guest













































































                              Comments

                              Popular posts from this blog

                              Long meetings (6-7 hours a day): Being “babysat” by supervisor

                              Is the Concept of Multiple Fantasy Races Scientifically Flawed? [closed]

                              Confectionery