Digital Assistant and Mobile

Get Involved. Join the Conversation.

Topic

    Sharath Chandra Gavini
    How to overcome the limits set by FacebookAnswered
    Topic posted February 11, 2019 by Sharath Chandra GaviniBlue Ribbon: 750+ Points, last edited February 11, 2019, tagged Bots 
    63 Views, 2 Comments
    Title:
    How to overcome the limits set by Facebook
    Summary:
    How can we overcome the limits set by Facebook for the number of characters, cards and buttons
    Content:

    Hi developers,


    There is a limit to the number of characters that are shown in the buttons, the number of bubbles shown and some other things. 


    This is causing me trouble in showing the options where my required button is more than 20 characters in length and also I need to display many options that exceed 11 bubbles.


    Is there any way that we get to show the full  options like we are able to in the web channel? I currently am sending the payload from the backend according to the number of  options. This method really works but I want to know if there is anything else that we can do to make this process easier by adding compatibility to unlimited bubbles and buttons.


    Thanks and regards,
    Sharath Chandra Gavini.

    Best Comment

    Grant Ronald

    Sometimes limits are there for a good reason.  I'd be seriously questioning your conversational design if you have >11 bubbles and quick replies > 20 characters.  In most of the guidelines I am aware of this would discouraged.  For a start, just imagine you were accessing that bot through Alexa or similar voice channel.

    My advice would be to rethink your design.  You may want to read this paper I've written on Conversational Design UX

    https://blogs.oracle.com/mobile/best-practices-and-tips-for-conversational-design-and-user-experience-in-oracle-digital-assistant

    Comment

     

    • Grant Ronald

      Sometimes limits are there for a good reason.  I'd be seriously questioning your conversational design if you have >11 bubbles and quick replies > 20 characters.  In most of the guidelines I am aware of this would discouraged.  For a start, just imagine you were accessing that bot through Alexa or similar voice channel.

      My advice would be to rethink your design.  You may want to read this paper I've written on Conversational Design UX

      https://blogs.oracle.com/mobile/best-practices-and-tips-for-conversational-design-and-user-experience-in-oracle-digital-assistant