Android iOS camera permissions - no response from the mobile user












1















In a website opened on the mobile device (can be chrome on Android and Safari on iOS) - I'm asking for the user permission to access the device's camera.



I have cases in which the user doesn't response to the permissions popup which is shown by the mobile OS



In case the mobile user doesn't response - the mobile web site is stuck - waiting for the user to response to the permissions popup



Can I define a timeout for the permissions pop-up after which the user will be redirected to another URL? Is it possible on both iOS & Android?










share|improve this question























  • Is it really necessary? The user won't be looking at the permission screen for long. They will have to act. Just wondering.

    – Rohit5k2
    Nov 14 '18 at 12:27











  • You will be surprised how often it happens

    – Hagai Ben Avi
    Nov 14 '18 at 12:29
















1















In a website opened on the mobile device (can be chrome on Android and Safari on iOS) - I'm asking for the user permission to access the device's camera.



I have cases in which the user doesn't response to the permissions popup which is shown by the mobile OS



In case the mobile user doesn't response - the mobile web site is stuck - waiting for the user to response to the permissions popup



Can I define a timeout for the permissions pop-up after which the user will be redirected to another URL? Is it possible on both iOS & Android?










share|improve this question























  • Is it really necessary? The user won't be looking at the permission screen for long. They will have to act. Just wondering.

    – Rohit5k2
    Nov 14 '18 at 12:27











  • You will be surprised how often it happens

    – Hagai Ben Avi
    Nov 14 '18 at 12:29














1












1








1


1






In a website opened on the mobile device (can be chrome on Android and Safari on iOS) - I'm asking for the user permission to access the device's camera.



I have cases in which the user doesn't response to the permissions popup which is shown by the mobile OS



In case the mobile user doesn't response - the mobile web site is stuck - waiting for the user to response to the permissions popup



Can I define a timeout for the permissions pop-up after which the user will be redirected to another URL? Is it possible on both iOS & Android?










share|improve this question














In a website opened on the mobile device (can be chrome on Android and Safari on iOS) - I'm asking for the user permission to access the device's camera.



I have cases in which the user doesn't response to the permissions popup which is shown by the mobile OS



In case the mobile user doesn't response - the mobile web site is stuck - waiting for the user to response to the permissions popup



Can I define a timeout for the permissions pop-up after which the user will be redirected to another URL? Is it possible on both iOS & Android?







android ios cordova camera android-camera






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 14 '18 at 12:25









Hagai Ben AviHagai Ben Avi

61




61













  • Is it really necessary? The user won't be looking at the permission screen for long. They will have to act. Just wondering.

    – Rohit5k2
    Nov 14 '18 at 12:27











  • You will be surprised how often it happens

    – Hagai Ben Avi
    Nov 14 '18 at 12:29



















  • Is it really necessary? The user won't be looking at the permission screen for long. They will have to act. Just wondering.

    – Rohit5k2
    Nov 14 '18 at 12:27











  • You will be surprised how often it happens

    – Hagai Ben Avi
    Nov 14 '18 at 12:29

















Is it really necessary? The user won't be looking at the permission screen for long. They will have to act. Just wondering.

– Rohit5k2
Nov 14 '18 at 12:27





Is it really necessary? The user won't be looking at the permission screen for long. They will have to act. Just wondering.

– Rohit5k2
Nov 14 '18 at 12:27













You will be surprised how often it happens

– Hagai Ben Avi
Nov 14 '18 at 12:29





You will be surprised how often it happens

– Hagai Ben Avi
Nov 14 '18 at 12:29












1 Answer
1






active

oldest

votes


















0














The responsibility of handling the UX in the right way falls on your shoulders as a developer.



The permission dialog in general provides 3 states




  1. Block

  2. Allow

  3. Dismiss


and lastly not a state but user can leave the pop up there without any activity



There is no way to get around this behaviour for obvious (or not) reasons.



Displaying the pop up at the time of accessing the "page" which unfortunately provides often very little context is hardly good UX. I suggest you launch the permission pop up only after you "explained" to the user why you require the access and how your website will benefit from it.



FYI: this is not just for mobile browsers but desktop as well






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    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',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53300205%2fandroid-ios-camera-permissions-no-response-from-the-mobile-user%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    The responsibility of handling the UX in the right way falls on your shoulders as a developer.



    The permission dialog in general provides 3 states




    1. Block

    2. Allow

    3. Dismiss


    and lastly not a state but user can leave the pop up there without any activity



    There is no way to get around this behaviour for obvious (or not) reasons.



    Displaying the pop up at the time of accessing the "page" which unfortunately provides often very little context is hardly good UX. I suggest you launch the permission pop up only after you "explained" to the user why you require the access and how your website will benefit from it.



    FYI: this is not just for mobile browsers but desktop as well






    share|improve this answer




























      0














      The responsibility of handling the UX in the right way falls on your shoulders as a developer.



      The permission dialog in general provides 3 states




      1. Block

      2. Allow

      3. Dismiss


      and lastly not a state but user can leave the pop up there without any activity



      There is no way to get around this behaviour for obvious (or not) reasons.



      Displaying the pop up at the time of accessing the "page" which unfortunately provides often very little context is hardly good UX. I suggest you launch the permission pop up only after you "explained" to the user why you require the access and how your website will benefit from it.



      FYI: this is not just for mobile browsers but desktop as well






      share|improve this answer


























        0












        0








        0







        The responsibility of handling the UX in the right way falls on your shoulders as a developer.



        The permission dialog in general provides 3 states




        1. Block

        2. Allow

        3. Dismiss


        and lastly not a state but user can leave the pop up there without any activity



        There is no way to get around this behaviour for obvious (or not) reasons.



        Displaying the pop up at the time of accessing the "page" which unfortunately provides often very little context is hardly good UX. I suggest you launch the permission pop up only after you "explained" to the user why you require the access and how your website will benefit from it.



        FYI: this is not just for mobile browsers but desktop as well






        share|improve this answer













        The responsibility of handling the UX in the right way falls on your shoulders as a developer.



        The permission dialog in general provides 3 states




        1. Block

        2. Allow

        3. Dismiss


        and lastly not a state but user can leave the pop up there without any activity



        There is no way to get around this behaviour for obvious (or not) reasons.



        Displaying the pop up at the time of accessing the "page" which unfortunately provides often very little context is hardly good UX. I suggest you launch the permission pop up only after you "explained" to the user why you require the access and how your website will benefit from it.



        FYI: this is not just for mobile browsers but desktop as well







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 14 '18 at 12:49









        Peter PajchlPeter Pajchl

        2,2321624




        2,2321624
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53300205%2fandroid-ios-camera-permissions-no-response-from-the-mobile-user%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            The Sandy Post

            Danny Elfman

            Pages that link to "Head v. Amoskeag Manufacturing Co."