Jotform feedback from a power user leveraging to mobile phones

  • Profile Image
    Asked on April 22, 2011 at 02:20 PM


    I work with Jotform all day creating solutions for companies. I am now working on solely mobile phone solutions for clients and have been working on Jotform 10-12 hours per day. Crazy, eh?

    I love working with it but felt it would be worthwhile to put down some of my findings re. mobile development.

    Jotform is optimised for mobile in that labels go to a top setting and some of the html tags are Iphone optimised, i.e. type="tel" that kind of stuff.

    I have worked tooth and nail to get a few Jotform elements to work in a mobile scenario but have, to my great misfortune and time spent, failed. Hopefully, they may be addressed and would be interested to any other users working on mobile

    They are as follows:

    1) The survey tool, form collapse, is ideally suited to mobile navigation. Unfortunately, it displays random freezing on Iphone, Opera mini and Android. I believe it to be a javascript problem. However, the problem is such that I cannot use the function due to a quality control issue. I will lose clients.

    2) The page break function is also ideaaly suited to mobile navigation. Unfortunately it suffers from a similar problem on extensive testing - that of showing the entire form in one page with fields rendered inaccessible. Shame - would be well useful. Again javascript which Iphone should be able to handle.

    3) There appears to be repeatedly and consistent problem with forms when one implements the shrink property on fields with the objective to get two fields on the same line. I am now wise to this, after spending many hours stripping a form down to find the rogue element. It would be a wise move for any of you good folk who have a form problem to locate any shrunk elements within the form. I believe the shrunk element renders iframed forms unusable if the form contains radio buttons. the show/hide elements on a radio function just migrate to the top of the form. Spent hours trying to get this to work

    4) If you can get away with using jotforms directly and not hide urls in iframes or via the embed option things seem to go much better on mobiles. However, adding forms via iframe or embed add another variable and I've been disapointed to find anomalous behaviour that is difficult to repeat consistently (nightmare) but that proves to be of great significance from a quality control point of view - simply put "would be the kiss of death on a mass scale"

    Hope this is useful to folks and the dev team - sorry to not be more specfic but one has to move quickly or one becomes an impromptu and unpaid tester compiling reports all day rather than getting on with their own business

    many thanks

    Regards Mark, Workflows

  • Profile Image
    Answered on April 22, 2011 at 10:39 PM

    Hi Mark,

    Thank you for this information I have forwarded this to our development team.
    This type of feedback is a great insight on how we can improve JotForm functionalities.

    Best Regards,


  • Profile Image
    Answered on April 23, 2011 at 03:07 AM

    wow, these are great feedback for us. I will ask our developers to prioritize this. If you can let us know the URLs of the forms and describe exactly on which mobile browsers they have problems, that should speed things up. Thank you.

    How do you test these on different mobile environments? We only have iphone and android phones in the office. Do you use some kind of virtualization for testing?

  • Profile Image
    Answered on April 25, 2011 at 05:55 AM


    I have an Iphone myself, an android emulator and lots of friends with different phones ;) and the below online service:

    You should be using, or at least try out, this:

    Regards Mark