Card Form: Input table's dot indicator is too close to each line

  • Profile Image
    Asked on December 14, 2020 at 04:10 PM

    4) The Input table on Mobile is poorly implemented. The fields are much too small (ideally, their width should be adjustable by the user), the text is barely readable (less than 10 pixels) and the "dots" that indicate the number of rows in the table are much too close to each other. (see below screen captures)


  • Profile Image
    Answered on December 14, 2020 at 05:09 PM

    The input table field's width is already relative to the form. Also, the sizes I believe are device-depended. The width of the form always depends on the screen size of the device where it is currently being accessed.

    Also. I am forwarding the concern regarding the dot indicators as a feature request. You will be notified here once an update is provided.

  • Profile Image
    Answered on December 14, 2020 at 08:34 PM

    Yes, they are using em's to set the sizes which are relative to the viewport, which is a poor decision from a UI perspective on mobile, since that could (and does) result in fonts that are too small to be legible. Minimum font size for any text on a mobile device should never be less than 16 pixels.

    FYI - We have abandoned the Card Form format and are using a traditional Jotform, which allows me to write CSS to produce a legible user experience regardless of the viewport size.

    There are just too many issues with the Card form, and no firm dates as to when they'll be corrected, for us keep waiting. Our client needs a reliable form up and running now.

    We've already wasted a week just finding and reporting issues with the Card form, and the fact that "swiping" disables conditional logic rules is totally unacceptable. So even if all the other layout and fonts size issues are corrected, that broken "feature" is a total deal-breaker for our using the Card form.

  • Profile Image
    Answered on December 14, 2020 at 11:58 PM


    We apologize for all the inconvenience in using the card layout form.

    I can see that all the features and issues are being forwarded to our developers to address it accordingly and we apologize as well if we can't give an estimated time for the implementation but we will keep you posted via those support tickets.

    We highly appreciate your understanding and taking another course to meet your requirements. Please do get back to us if you need further assistance with your forms. Thank you.

  • Profile Image
    Answered on December 15, 2020 at 12:14 AM


    Yes, thank you. I've gotten about 50 "we apologize" and "we appreciate your patience" messages from Jotform in the past two weeks.

    What I find annoying is that this Card form style layout was clearly NOT READY for deployment, and yet Jotform put it out anyway, and is basically relying on its users to do all the beta-testing that should have been done by your development team!

    I can understand that there may be some issues they cannot foresee, but something as glaring as having conditional logic ignored when users swipe to go forward or backward to next and previous questions on mobile devices is unforgivable! Conditional logic is a MAJOR FEATURE, so simply not have working when users swipe a form on mobile devices is ridiculous!

    It should either be made clear on the website that conditional logic doesn't work when swiping on the Card form, or the swiping capability should be disabled until the developers figure out a solution.

    In my case, it made the Card form I created completely useless! 20 hours of work down the drain. And a very upset client who I had to tell after a week of waiting that I needed to start over from scratch, building a new form via a traditional single page layout.