Forum Discussion

TylerFoy81's avatar
TylerFoy81
Qrew Trainee
20 days ago

Mobile Screen Jumping

I have a form that generates approximately 500-600 submissions per day. The form currently contains 320 fields, 55 form rules, 100 lookup fields, and around 80 image fields.

I've been troubleshooting a significant issue on mobile devices where selecting any multiple-choice question causes the screen to jump erratically. To isolate the problem, I've tried:

  • Removing all image fields
  • Reducing the total field count
  • Creating a simplified version with only 5-6 questions and roughly 30 fields

Even with the stripped-down version, the screen jumping still occurs whenever a multiple-choice field is selected on mobile.

Has anyone experienced something similar or have suggestions on what might be causing this? I'm trying to determine whether this is related to form configuration, form rules, lookup fields, browser behavior, device-specific issues, or a platform limitation/bug. Any troubleshooting ideas would be greatly appreciated.

Forms

3 Replies

  • Denin's avatar
    Denin
    Qrew Officer
    19 days ago

    Without looking at the form, it's hard to troubleshoot it.

    But based on your description alone, sounds like the DOM objects are changing height as they load in and it causes the browser scroll position to jump around.

    Some questions:

    • Your multiple choice questions and answers, how long are they?
    • What is the field type? Is it actually multiple choice? Have any multi-select fields?
    • Do you have rich text content on the form? Not necessarily formulas, but any content like rich text blocks.
    • What browser are you using on mobile?
    • Have you recreated this problem on more than one device, network, and browser?
    • TylerFoy81's avatar
      TylerFoy81
      Qrew Trainee
      19 days ago

      browsers - Safari, Chrome and edge. Iphone, Androids and android tablets 

      The form is currently configured with approximately 40 Rich Text fields, each of which references a lookup field. The intent is to allow each location to manage its own custom questionnaire. When a user selects a specific form, the relationship pulls down the form name and up to 40 associated questions.

      Each Rich Text field then displays the corresponding question in bold using IF statements. The answer field for each question is a multiple-choice selection with three options:

      • Good
      • Bad
      • N/A

      If the user selects "Bad," the associated Rich Text question changes to red. No other formatting or behavior is applied.

      To troubleshoot issues, I have removed much of this formatting and logic from the mobile form, which has helped somewhat. However, I am still seeing screen jumping from mobile devices.

      My other concern is the number of form rules being used (55). Currently, each question and its corresponding answer field are hidden unless the question contains data. This allows the form to dynamically display anywhere from 5 questions to 40 questions, depending on the questionnaire selected.

      I'm beginning to suspect that both the heavy use of Rich Text fields and the large number of form rules are contributing to the problem.

      Is there a more efficient way to achieve this same functionality without relying on so many form rules? Ideally, I need a solution that still allows the form to dynamically show only the questions associated with the selected questionnaire while improving performance and stability on mobile devices.

      • Denin's avatar
        Denin
        Qrew Officer
        19 days ago

        For rich text fields, form sections, or any elements that display images, you may want to define a fixed height and width in the HTML if you aren’t already. This can help stabilize layout rendering and reduce the chance of the scroll position shifting unexpectedly.

        Regarding moving away from form rules, it really depends on what the rules are doing. In some cases, you might be able to rely on the Edit/View/Add visibility options instead of conditional logic. Creating separate forms can also help reduce complexity. Roles and permissions may cover certain scenarios as well, and table rules could be an alternative depending on your workflow. Another option is to consider a custom-coded form that submits data to Quickbase via the API.

        That said, the Quickbase mobile experience has historically had limitations. It’s possible you’re running up against the practical boundaries of what the native mobile form can do without custom code.