Where the design community meets.
San Diego UI/UX Designer Joined 11 months ago
This also reminds me of the guy who made entire digital paintings from a spreadsheet
I've been saying this for years! When people ask "Do designers need to know how to code?", my response is always "you're asking the wrong question. We should be asking if designers should understand business?".
I've been using for Figma for a year now and I definitely noticed the changes right away, my first reaction was "this is different" but not in a bad way but not in an improvement way either. The change hasn't affected my worfklow at all, I'm still able to do the same things as I've done before because I've already been conditioned to where everything lives. For the most part, things are still in the same spot with exception of a few items. So the lack of borders don't bother me since I know where everything is. I do wish they prioritized fixing other things instead of doing this UI refresh but hey, we all know that's not up to the designers but the higher ups.
Sorry to hear that you think the contrast is bad but objectively speaking, it does pass the contrast minimum if you inspect the element in chrome browser tools (or plug in the colors in your favorite WCAG tool)...
I think you should quit before you/company gets more invested and then it'd be "harder" to quit. I say because I've never worked at a place where I felt the need to quit after a week...not even after a few months....to feel like you need to quit after a week is pretty bad in my opinion. If what you're saying is true where everything has a lot of red tape, I don't see that changing overnight thus I don't see it getting better if you hang in there for a bit longer.
People make it a big deal about quitting so soon, but when was the last time you've known someone that quit so soon and you're still mad at them? I've known a handful of people who stayed at their places for a really short period but it shouldn't all be their fault. It's also on the company for not showing the entire culture during interview process. Most people are busy anyways and there's so many other things to occupy their mind. A few months from now, most people won't be fussing over someone who left- they'd be worried about meeting their project deadlines, or picking up their kids, or planning their next trip to their hometown. I always ask myself "how much will this matter 1 month from now? 3 months from now? A year from now?". Most people forget and move on.
Ok, that definitely adds clarity. We're currently doing that for mockups where components are coming from the Design System. But it's also good to know where you're coming from in the sense that you don't treat mockups as the source of truth (always up to date).
How well does this process work for the designers? Say I need to mockup some screens that are using existing icons and images, so does this mean I have to go to the repo, find where it's located, download the asset onto my local machine, and then import it to my design document? It seems like a lot of steps
Make one for Figma please!!
Out of curiosity, have you gave this feedback to the Zeplin team directly? Because I've certainly given them my feedback but not through this medium, but on their website and they actually respond right away and implemented my feedback a few months later
According to this survey (http://uxtools.co/survey-2018#handoff), Zeplin is still the industry preferred handoff tool. I don't use Zeplin anymore cause Figma gets the job done now but I'd still recommend Zeplin over InVision. I tried InVision Studio when it first got released to the public and it was really laggy, so I preferred the responsiveness of Zeplin.
If anything, I feel like Zeplin isn't the only app that's going to be crushed. It's Sketch and InVision.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.