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
Right now we only show a loading splash screen when users click on the opensauced logo:
If users want to navigate the rest of the site (which can be a bit slow at times) there's no indication that the page is loading.
Suggested solution
We could really use some affordance to make it clear to the user that when they click on a link to navigate to somewhere else in the page, that page is loading. Otherwise it feels like you click on stuff but nothing happens.
As much as I like the pizza splash screen, I think it does remove the user from context and adds some cognitive load, making it feel like the page takes longer to load than it actually does.
A suggested solution would be to have a loading animation like Github's -- a loading bar right below the url box (see the blue loading indicator):
Example
(pls ignore weird background texture of the gif, focus on orange bar at the top)
Type of feature
🍕 Feature
Current behavior
Right now we only show a loading splash screen when users click on the opensauced logo:
If users want to navigate the rest of the site (which can be a bit slow at times) there's no indication that the page is loading.
Suggested solution
We could really use some affordance to make it clear to the user that when they click on a link to navigate to somewhere else in the page, that page is loading. Otherwise it feels like you click on stuff but nothing happens.
As much as I like the pizza splash screen, I think it does remove the user from context and adds some cognitive load, making it feel like the page takes longer to load than it actually does.
A suggested solution would be to have a loading animation like Github's -- a loading bar right below the url box (see the blue loading indicator):
Example
(pls ignore weird background texture of the gif, focus on orange bar at the top)
Additional context
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: