Infiniti Go (iOS/Android)

There are several considerations while designing a form to be used by Infiniti Go.

Design for the device

What sort of device will your form be used for? A web browser is very different to a phone. A layout which works well for a desktop browser won't necessarily work for a phone. Form design needs to be considered and tested from the beginning of a project.

Performance

Excessive layout elements can have an impact on how quickly the page is displayed and updated (after conditions). One of the slowest operations on a mobile device is the drawing of visual elements. Every layout and question element will be rendered even if they are conditionally invisible. For best performance, it is recommended that a form is broken into as many pages as possible to reduce rendering overhead.

Example:

A designer would like to have question text take up 35% of the screen. If you were to use a section with column width percentages the layout tree would like this:

Example 1

* Page
 * Section
   * Column
     * Question Text
   * Column
     * Question Text Box

If you were to use the left question text element.

Example 2

* Page
  * Question Text
  * Question Text Box

Example 2 has three fewer elements than example 1, which over a large project can save a significant amount of rendering time.

Data sources

There are several ways to configure a data source for mobile use. It's important you use the right method for your user experience. See the article on Infiniti Go for more information.