Be nice. Or else.
Lead Front End @ FiscalNote Joined over 3 years ago
Dan hasn't posted any stories yet.
This is a conversation we're currently having in our org. @miles, when branching out or deviating away from current guidelines, what kinds of rules/principles do you apply to make that decision? From a teaming perspective, it seems difficult to know and defend when to make a decision to deviate if there isn't a set of rules/principles on when and how to deviate from current design system guidelines.
haha thanks for the nostalgic moment
staring at this as it loops is strangely therapeutic
I'm speaking as a client-facing engineer on a product focused team. When building with speed, it is easy to point to a tool and say, "let's just use this and save time". My philosophy is that the design should come before the tool is chosen. Otherwise, there isn't sufficient context as to whether or not a tool/framework/plugin/addon/etc... is either insufficient, sufficient enough, or overkill. Also when I say "design", I mean when it is in its final stages for us: when it has been user-validated to a certain degree of confidence and has been given engineering feedback about feasibility.
love Grovemade products and their site design is quite simple and intuitive to use also
wow, this is well executed, and actually fun!
wouldn't that mean you're not scrolling at all :O
Love the idea. Couple things:
I wasn't sure it was working after I selected the locations. An indication that something was processing would be great.
After the second location is set (pressing enter), you need to click somewhere else in the form for it to continue. If you physically click on one of the items in the autocomplete dropdown instead of pressing enter, it has the desired affect.
edit: just realized (2) has been noted above haha
Be nice. Or else.
Designer News is a large, global community of people working or interested in design and technology.