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
Some of the sub-screens we have are a bit sparse. One of the suggestions was to use a drawer on desktop instead of a full-screen navigation.
In this mock-up, we see a settings screen on the left. If the user clicks "Detailed settings", the middle screen slides up from below. The alternative would be to use a drawer instead, which is what the third screen shows.
Considering the question of consistency, would we just always use a drawer or only if the screen is somewhat empty? We'd have to figure out a logic for that. If we sometime use full screens, and sometimes drawers, we'd have to ensure that the UI feels intuitive (predictable in this case).
Drawers exist as a mobile UI pattern, but are not very common. So far, we just kept everything consistent across desktop and mobile, for simplicity of design and coding. Because of this, I think it can be good to revisit some of the patterns as we keep working on the app. Especially as we start using it heavily, we may realize that some design choices did not pan out as we thought they would. For this specific one, it would be good not to make a change on the worst-case scenario (the most empty screen in the app), but all uses of this pattern, and take it from there.
The text was updated successfully, but these errors were encountered:
Some of the sub-screens we have are a bit sparse. One of the suggestions was to use a drawer on desktop instead of a full-screen navigation.
In this mock-up, we see a settings screen on the left. If the user clicks "Detailed settings", the middle screen slides up from below. The alternative would be to use a drawer instead, which is what the third screen shows.
Considering the question of consistency, would we just always use a drawer or only if the screen is somewhat empty? We'd have to figure out a logic for that. If we sometime use full screens, and sometimes drawers, we'd have to ensure that the UI feels intuitive (predictable in this case).
Drawers exist as a mobile UI pattern, but are not very common. So far, we just kept everything consistent across desktop and mobile, for simplicity of design and coding. Because of this, I think it can be good to revisit some of the patterns as we keep working on the app. Especially as we start using it heavily, we may realize that some design choices did not pan out as we thought they would. For this specific one, it would be good not to make a change on the worst-case scenario (the most empty screen in the app), but all uses of this pattern, and take it from there.
The text was updated successfully, but these errors were encountered: