
Following best practices while creating a form helps provide a clear and smooth experience for users. A well-structured form is easier to understand, complete, and manage.
This article outlines recommended practices for configuring pages, form steps, elements, and the overall form flow in the Form Builder.
Only ask for information that is required for your use case.
Avoid adding unnecessary fields, as lengthy or complicated forms may discourage users from completing them.
Before adding a field, consider:
For forms that require multiple fields, divide the information into logical sections using Form Steps.
For example:
Grouping related fields together makes the form easier for users to understand and complete.
Best Practice: Avoid adding too many fields to a single step.
Add a meaningful Page Title to help users understand what information is required on each page.
Use the Page Description to provide additional instructions when necessary.
For example:
Page Title: Product Details
Page Description: Please enter the details of the product you purchased.
Keep titles and descriptions short, clear, and easy to understand.
Field labels should clearly explain the information users need to provide.
For example:
Recommended:
Avoid:
Clear labels help reduce confusion and incomplete submissions.
Select the most suitable element for the type of information you want to collect.
For example:
Using the correct field type helps improve data accuracy and provides a better user experience.
Mark only essential fields as Required.
Requiring users to complete unnecessary fields can make the form difficult to complete.
Best Practice: Make a field mandatory only when the information is necessary to process the submission or complete the required workflow.
When using elements such as Dropdowns, Radio Buttons, or Checkboxes, keep the options easy to understand.
Avoid:
Where possible, arrange options in a logical order.
Use Conditional Rendering to show fields only when they are relevant to the user.
For example, if a user selects Yes for a particular question, you can display an additional field to collect more information.
This helps keep the form clean and prevents users from seeing unnecessary fields.
Best Practice: Use Conditional Rendering only when it simplifies the form flow. Avoid creating overly complex conditions that may be difficult to manage.
Arrange pages and fields in the order users would naturally provide the information.
For example:
A logical flow helps users understand what is expected at each stage.
Use Content Images and Rich Text to provide useful information or improve the visual appearance of the form.
However, avoid adding too much content that distracts users from completing the form.
Use images and text to:
The Thank You Page should clearly confirm that the form has been successfully submitted.
You can include:
For example:
Thank you for your submission!
Your information has been successfully submitted. You will receive a confirmation shortly.
Always use Preview before publishing the form.
Check the following:
Test the form from a user's perspective to identify any confusing or unnecessary steps.
Click Save after making changes to avoid losing your configuration.
When making significant changes, review the complete form again before publishing.
Before publishing your form, make sure that:
All required fields have been configured.
Field labels are clear and easy to understand.
Page titles and descriptions are configured correctly.
Form steps follow a logical sequence.
Conditional Rendering rules have been tested.
Buttons and navigation work correctly.
The complete form has been reviewed using Preview.
All changes have been saved.
By following these best practices, you can create forms that are clear, organized, and easy for users to complete. A well-structured form also helps improve data accuracy and provides a smoother overall user experience.