Be nice. Or else.
Design Director Joined over 2 years ago
Andrew hasn't posted any stories yet.
Atomic design helps somewhat with things like this. The header bar, bottom bar (if any) and general sizing of the modal body (including scroll) are atoms and molecules. The modal frame is an organism based on these constituent component. The form you'll nest inside the modal is ALSO an organism (comprised of buttons, inputs, labels, errors, etc). Together they create a general template (or pattern). And the final piece with real elements is a page.
You can have multiple modal organisms if your app calls for that. That's OK... but question why you need two instead of one. Atomic design isn't perfect by any means (it's taxonomy is quite clumsy) but it's a common language to help talk through front-end hierarchy like this.
Generally a dev and a designer will sketch out solutions together, and reconcile their ideas with the existing design system (where possible). After this is done they write JIRA tickets. The designer will attach any Zeplin links to a keylined (spacing, font-size, variables, etc) design that matches our front-end system.
Developer does their thang. If problems arise they sketch things out or increase scope (if scoping down doesn't provide a satisfactory outcome). Developer loops the designer in w a demo or link to staging to QA the thing and the ticket is closed.
Zeplin is useful for me because I can see when new work is being posted so I can make sure the designers are collaborating and being consistent. Generally the Zeplin file is the thing that's getting built (rather than a hypothetical blue sky flow in InVision or Sketch). That's our "API" of sorts between everyone.
We also have the ability to write usability citations to people who are willfully doing short term fixes against a deadline. As a design director this was very helpful. This lets them do the hack, finish the next project, and then return. The kicker being they actually can't start any new projects or create any more usability citations before their squad can break new ground. This has been very seldom used since the culture shifted towards usability and testing. At the beginning though it helped the PMs know how to make decisions when sales and CS may be breathing down their neck for a new feature (a performance payoff for their team).
I actually enjoy using Zeplin as a separate handoff. Creates a nice contract when something is exploratory (Sketch, or Invision) and when it's actually going to production (Zeplin).
Uhh most modern tech stacks were built off of Mac's Terminal. Also most dev's don't need Sketch files—they need a breakdown like Zeplin, a flat spec (ie. a screenshot), or work in tandem w a designer.
I'm not hitching my wagon to Adobe again, btw—doesn't matter how good XD is. The XD team is chugging along well, but Adobe felt like an absentee parent in the UX and product design industry for far too long. I assume if they owned the market and they'd stop innovating.
When I open up InVision Studio, Framer, etc. I come in on a wind of hype and all I see is Sketch + some design trendy. Sketch + libraries, Sketch + animation, Sketch + react native, etc. But so far it's not been enough to make me invest in a switch.
I honestly just enjoy making stuff in Sketch more.
Ha—this is cool. It actually reminds me a lot of Tony Hawk Pro Skater 2. Even better the neat transition actually progressively discloses more information about the skateboard—keeping the initial state clean while also providing additional utility.
Slack's modals break most of the rules outlined in this.
Yeah except everyone here was LITERALLY DYING to have downvotes. I remember posting about how dumb it was —no, it's not going to stop spam, and it encourages people to downvote rather than encouraging them to just post some good stuff to the community. It's a silly concept for a website like Designer News.
Designer News isn't dying though. It's just a place people go when they're bored (like me now, with 10 minutes free I don't know what to do with).
You don’t need to code. There’s a reason why designers tend to give it up when they get a job on a team: generalists just aren’t as good as specialists.
I direct a fairly large team now. The designers on the team that consistently nail execution don’t know any code. They just know how to negotiate and provide measured front end specs if a dev isn’t as comfy w front end.
Did you use the exact same hex that he used in the video or just something that looked the same?
I’ve had bad luck rendering things out of chrome headless consistently in the same way. This may be a limitation or web based apps for certain hexes.
Be nice. Or else.
Designer News is a large, global community of people working or interested in design and technology.