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 risk creating more work when it comes to building the screens/interactions
because engineers will be tempted to re-create the screens as they are instead of using built-in MaterialUI Components.
After opening that previous link in Figma you will see the following:
"Thank you for duplicating our free demo of the MUI for Figma: a comprehensive component inventory for Figma, including over 1,500 unique elements that cover the full range of states and variations of each component."
On the plus side, I'm SUPER keen on the idea of using a UI component library like Material UI to keep the MVP functional but also usable and consistent so that poor UI design doesn't detract from what we're actually trying to test, ie so it's not fugly.
Not to mention time gains from not having to manually write the CSS for every component from scratch.
At present our
Figma
designs are using basic boxes we created by hand:Direct link to Figma page: https://www.figma.com/file/WrpkKGJNYZbeCzMRDVtvQLbC/dwyl-app?node-id=246%3A2
It's not ideal. 😕
We risk creating more work when it comes to building the screens/interactions
because engineers will be tempted to re-create the screens as they are instead of using built-in
MaterialUI
Components.https://m3.material.io/develop/flutter
So ...
Todo
MaterialUI
toFigma
🔍The text was updated successfully, but these errors were encountered: