Closed ggeisler closed 3 years ago
I believe this ticket is fully implemented with #89 merged. @thatbudakguy is writing up some accompanying documentation in #102 for working with this in local dev. Current intervals are set to 5 minutes to initiate the unattended experience flow, then 1 minute per slide.
closing, since this is implemented and documented in the README.
Related conceptual discussion in #18. This ticket also assumes the basic auto-play interaction has been worked out.
The auto-play interaction ensures that if a visitor has started an experience but walks away at some point, that experience will auto-play through the remainder of its screens and end up back on its initial screen.
To better advertise that the unattended wallscreen includes more experiences than just the one currently displaying its home screen, we don't want to remain on a given initial screen too long. But I'm also not sure we want to auto-play through each experience either, because that means the "Begin [experience]" button will be relatively infrequently visible, and the wallscreen will at times (e.g. when the oral history experience is active) display one experience for a significant amount of time. Instead, to advertise the wallscreen when it's unattended, I suggest the main interaction is simply to rotate through the initial screens of each experience variant, pausing on each for some brief amount of time.
Definitions
Experience variant home screen: This is what we've been mostly been referring to as the "initial screen". Each experience variant has a home screen, where the info card includes the title/subtitle of the experience variant and a "Begin [experience]" button, and the content area includes some sort of imagery (details of which is TBD).
Wallscreen is unattended: When an experience home screen is currently displayed and there has been no user interaction for
{UNATTENDED_TIME}
(e.g., 25 seconds - should be a variable we can easily adjust after testing or observation when in production, etc.).Home screen queue: We have three distinct experience types, with a default order of
slideshow
,guided tour
, andoral history
. Each type will have one or more variants (depending on which wallscreen we're talking about, and how many experience variants the curators can complete). The queue is the order of the experience variants, going through each column of each row in order (slideshow A, tour A, oral history A, slideshow B, tour B, etc.), skipping any columns where the variant for that experience hasn't been defined:Here's a visual representation of the same thing (though I'm using a different default slideshow variant here):
Suggested flow when wallscreen is unattended
Despite all my explanation above, I think the idea is pretty simple (assuming I'm not missing something!):
{UNATTENDED_TIME}
timerIf the "More info" button is selected, I think the
{UNATTENDED_TIME}
timer is reset, but also that control goes to the timer used for the "More info" overlay. (Or to put it another way, once the "More info" button is selected and the overlay is displayed, we're no longer in the state required for an "unattended experience" since we're not on the home screen; we'd have to wait for the overlay to be removed to be back in the state where the flow above is relevant.)