Return to Answer

added 12 characters in body

Source Link

edited Oct 24, 2020 at 16:59

3.3k
5
23
36

Example 1 is a better option for few reasons. Primarily "less is better on the UI"

ItsIt's a standard interaction which is based on progressive disclosure pattern. It is better to remove unnecessary content on interface till itsit's needed (i.e in this case only if user choosechooses to "deliver as attachment", attachment option shows up. tillTill then itsit's hidden).
The connection between the related content and its parent is immediately obvious. In the second option you have bring extra design elements to show the relation, thereby further adding noise to the interface.
Other concerns of scrolling isare in fact a bigger and serious problem in Example 2. In case if the select attachment goes out of the scroll, then the user will never know that the related option has opened below the scroll.

However, Example 1 will only work if the related content is a small task such as 'attaching a file",. If the related content is more complex then this fails.

Example 1 is a better option for few reasons. Primarily "less is better on the UI"

Its a standard interaction which is based on progressive disclosure pattern. It better to remove unnecessary content on interface till its needed (i.e in this case only if user choose to "deliver as attachment", attachment option shows up. till then its hidden).
The connection between the related content and its parent is immediately obvious. In the second option you have bring extra design elements to show the relation, thereby further adding noise to the interface.
Other concerns of scrolling is in fact a bigger and serious problem in Example 2. In case if the select attachment goes out of the scroll, then user will never know that the related option has opened below the scroll.

However, Example 1 will only work if the related content is a small task such as 'attaching a file", If the related content is more complex then this fails.

Example 1 is a better option for few reasons. Primarily "less is better on the UI"

It's a standard interaction which is based on progressive disclosure pattern. It is better to remove unnecessary content on interface till it's needed (i.e in this case only if user chooses to "deliver as attachment", attachment option shows up. Till then it's hidden).
The connection between the related content and its parent is immediately obvious. In the second option you have bring extra design elements to show the relation, thereby further adding noise to the interface.
Other concerns of scrolling are in fact a bigger and serious problem in Example 2. In case if the select attachment goes out of the scroll, then the user will never know that the related option has opened below the scroll.

However, Example 1 will only work if the related content is a small task such as 'attaching a file". If the related content is more complex then this fails.

Source Link

answered Oct 23, 2020 at 4:30

aswamy

Example 1 is a better option for few reasons. Primarily "less is better on the UI"

Its a standard interaction which is based on progressive disclosure pattern. It better to remove unnecessary content on interface till its needed (i.e in this case only if user choose to "deliver as attachment", attachment option shows up. till then its hidden).
The connection between the related content and its parent is immediately obvious. In the second option you have bring extra design elements to show the relation, thereby further adding noise to the interface.
Other concerns of scrolling is in fact a bigger and serious problem in Example 2. In case if the select attachment goes out of the scroll, then user will never know that the related option has opened below the scroll.

However, Example 1 will only work if the related content is a small task such as 'attaching a file", If the related content is more complex then this fails.