[Evolution] Component Select #1989
LucasAlbuquerque0
started this conversation in
Proposals
Replies: 2 comments 9 replies
-
This is because in mobile the select opened is used with native pickers. This picker is depends on browsers and OS |
Beta Was this translation helpful? Give feedback.
0 replies
-
I have two questions @yceballost |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Goal
As the Select Desktop component, the Select Mobile component receives "Status: Opened".
Context
Since the mobile component does not contain the exposed Menu, some designers end up having to create their own Menu to use within visual applications, leaving room for errors and problems when searching for these components and mainly causing visual divergence during QA.
Even having the Menu component, it ends up being an extra step of knowledge that some designers end up forgetting or not knowing and tend to make mistakes.
Impact
Problems when doing QA of the screens, where there is a discrepancy between what is presented in Figma and what is seen in the app
Discussion Questions
To have consistency between mobile and desktop components, they need to be reflective. Do you consider the evolution valid?
Additional considerations
Visual presentation of the problem
To maintain the same consistency between components, adding the same status on mobile
Do you have a visual proposal?
No response
Beta Was this translation helpful? Give feedback.
All reactions