Some pros and cons of appearance='field-list'

A client is interested in having as many questions as possible show up
on the same page.

Although the attribute appearance solves this () I was wondering if there are any extremely
good reasons not to use this.

My own Pros and cons lists consists of
Pros:

  1. Less swiping for long surveys

Cons:
2) Questions depending on skip logic cannot be put in this group

Are there any other blatantly obvious points that I'm missing? Thank
you for your time.

Note that skip logic can be applied to the entire field-list group.

A more general caveat is that once the field-list is rendered,
any calculated fields or text labels that include field-value substitutions
(e.g., with elements), and any validation tests won't be evaluated
while on this page. Validation tests are applied, in order, only when you
swipe forward to the next screen.

So you should generally avoid displaying Q1 and Q2 on the same screen if Q2
in any way depends upon the value of Q1.

Mitch

ยทยทยท On Mon, Apr 16, 2012 at 11:45 AM, dm03514 wrote:

A client is interested in having as many questions as possible show up
on the same page.

Although the attribute appearance solves this () I was wondering if there are any extremely
good reasons not to use this.

My own Pros and cons lists consists of
Pros:

  1. Less swiping for long surveys

Cons:
2) Questions depending on skip logic cannot be put in this group

Are there any other blatantly obvious points that I'm missing? Thank
you for your time.

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com