Button for next-all

[oczki]

Usability testing revealed that users tend to refresh the whole page instead of clicking on section buttons. When asked why, they said they are aware of the buttons, but they wanted to see a complete new set. Seems that the site might be used for a complete improv scene definition, not just single aspects of it.

Action: Add a mechanism enabling the user to set a new word in every category at once. There are a few ideas how to approach this while keeping the UI minimal and consistent.

Ten thousand hours in MS Paint

A) Put the next-all button on top

Pros

• The button will be easily visible
• If people use it, will cause less data transfer / read ops
• Will add a space for other stuff: logo, link to the about page

Cons

• Actually useful information (words) are pushed down the screen
• Last few sections will get cut out even more

B) Put the next-all button at the bottom

Pros

• Actually useful information (words) stay the most visible
• Will work as a footer, where other information might go: logo, about page, etc.

Cons

• Might not be visible at all, which will invalidate any benefit that such a button would add
• People already rarely go to the bottom of the page, as that's where the least useful section resides (random dictionary word)

C) Custom pull-down action

Example: https://ebidel.github.io/demos/chatbox.html

Pros

• Takes zero space from existing layout
• Overrides the action resulting from actual users' behavior, causing the page to behave virtually the same, but without the downsides of page loads / file reads

Cons

• Expensive to implement
• May cause confusion at first
• Might not work on all mobile browsers
  • Need to check for overscroll-behavior-y support on client side
• No equivalent for desktop browsers - need for a regular button there

[oczki]

D) Redesign everything again

+---------------------+
| <   inspirac.je   > |
|_____________________|
|                     |
|      rzeczownik     |
| <   BARBARZYŃCA   > |
|                     |
|       miejsce       |
| <    BIUROWIEC    > |
|                     |
:         ...         :
.                     .

Center everything and add arrows on both sides. This would result in loss of "next" and "previous" buttons - both would work as "navigate to the side", resulting in moving around the (cyclic) word array. This would also be a starting point for swipe-based navigation.

Pros

• Works equally well for both left- and right-handed users
  • I completely missed the fact that not everyone holds their phone in left hand
• Nice place for a logo or whatever at the top
• Consistent look
• Possibly more place for the word, especially if the arrows were to be moved to the sections' headers

Cons

• Expensive to implement
• Even though I know how it will end up working, this is still confusing as all hell to me
• The header moves all the useful words down the page
• Longer words (not fitting the width of the viewport) will overflow on both sides of the screen
  • SVG text auto-scaling would have to be brought back
• No place for a link to the about section