You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We went live at one of our larger campuses today with NextGen Checkin. There is an issue and a usability issue that go together. When a person gets to the end of the checking in, two things were happening:
The amount of time it took to go refresh back to the Start screen so the next person can checkin was different on different kiosks. Some were 8 seconds, some were 15. We have our refresh interval set to 10 on the checkin configuration and on the block setting for the NextGen checkin screen (not sure if these are the same setting). Plus, I don't want to make it any shorter than 10 if it is going to also impact how long they can be idle on a screen.
Because some of them were taking 15 seconds, kiosks appeared unusable to people. They are used to seeing a big Done button on the screen which most of them selected before they walked away. Now, the button says Home in the upper right corner and is gray / blends in. Even kids were clicking our X logo in the upper right corner to try to go home since that is universally the "home" option on a website. When I pointed out the Home button, they were surprised.
Actual Behavior
Kiosks refresh back to start page at different timings/intervals which are too long and left the kiosk unusable to the next user because the Home button is not obvious at all or natural language to the user.
Expected Behavior
Kiosks all refresh back to the Start page on the same timing after a checkin has occurred.
The Home button is made much more obvious. Thoughts: Add a Done button back to the bottom of the screen after checkin is complete OR change the Home button to be the same color as the main theme color AND change the word to Done OR some other idea you come up with that is user tested and works.
Steps to Reproduce
Go to NextGen checkin
Check a kid in on multiple different kiosks that are checking into the same schedule
The refresh time back to Start varies and the Home button is not obvious
I could not try this on a demo site (the refresh issue).
Issue Confirmation
Perform a search on the Github Issues to see if your bug or enhancement is already reported.
Reproduced the problem on a fresh install or on the demo site.
Rock Version
Rock McKinley 16.8 (1.16.8.1)
Client Culture Setting
en-US
The text was updated successfully, but these errors were encountered:
kimlongcr
changed the title
NextGen Checkin-Kiosk Timeout and Home Button not Obvious
NextGen Checkin-Kiosk Refresh is Random and Home Button not Obvious
Feb 23, 2025
I'm a little confused by this... is the image above showing the giant orange "done" button what you're suggesting should be added to Next Gen, or is that an actual screen shot of what it does now?
Description
We went live at one of our larger campuses today with NextGen Checkin. There is an issue and a usability issue that go together. When a person gets to the end of the checking in, two things were happening:
Actual Behavior
Kiosks refresh back to start page at different timings/intervals which are too long and left the kiosk unusable to the next user because the Home button is not obvious at all or natural language to the user.
Expected Behavior
Kiosks all refresh back to the Start page on the same timing after a checkin has occurred.
The Home button is made much more obvious. Thoughts: Add a Done button back to the bottom of the screen after checkin is complete OR change the Home button to be the same color as the main theme color AND change the word to Done OR some other idea you come up with that is user tested and works.
Steps to Reproduce
Go to NextGen checkin
Check a kid in on multiple different kiosks that are checking into the same schedule
The refresh time back to Start varies and the Home button is not obvious
I could not try this on a demo site (the refresh issue).
Issue Confirmation
Rock Version
Rock McKinley 16.8 (1.16.8.1)
Client Culture Setting
en-US
The text was updated successfully, but these errors were encountered: