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
{{ message }}
This repository has been archived by the owner on Jul 9, 2019. It is now read-only.
Problem:
The space creation and initial screen for the launcher are both black overlays that cover the OSIO top bar. Having gone through two screens similarly formatted the user believes that they should expect this style of screen as the configuration experience.
However, following the import or new project selection the user is dropped into a vertical "wizard" that is no longer an overlay and switches to main content on white background.
The effect is jarring and confuses the user because it seems to indicate that they're in a different part of the product and doing some other type of config (or perhaps not doing config at all?).
Possible solution:
It would be clearer to maintain consistency with:
Overlay or non-overlay
All black or black-nav with white-input area
The text was updated successfully, but these errors were encountered:
Yep, main triage here and we'll put it in the appropriate component repo as necessary. Sending to Erik to figure who he'd like to have handle it and what to do. :)
Problem:
The space creation and initial screen for the launcher are both black overlays that cover the OSIO top bar. Having gone through two screens similarly formatted the user believes that they should expect this style of screen as the configuration experience.
However, following the import or new project selection the user is dropped into a vertical "wizard" that is no longer an overlay and switches to main content on white background.
The effect is jarring and confuses the user because it seems to indicate that they're in a different part of the product and doing some other type of config (or perhaps not doing config at all?).
Possible solution:
It would be clearer to maintain consistency with:
The text was updated successfully, but these errors were encountered: