5 ms·

From UX perspective, it's one of the best tools for managing the design process. 1-click to update / push mockups from Sketch. Ability to do light interactive m

by daleco 8y ago

From UX perspective, it's one of the best tools for managing the design process. 1-click to update / push mockups from Sketch. Ability to do light interactive mockups, commenting, and CSS specs. We've been testing most of the tools on the market (Zeplin, UX Pin, Avocode...). InvisionApp beat all of them.

jbob2000 8y ago
I am happy that you found some use for it. Have you asked your devs how they use it? I do understand that mockups aren't just for developers, but you might be going to all that expense and effort for nothing. When I joined my team, after 6 months the designers asked me for some feedback on how I was using invision and I said it's just a screenshot host and they were shocked. But all the design specs are in there!. Yeah great, I know what 3em padding and 16pt font looks like, I'm not spending 2 hours poking through a clunky web app to find that out. The CSS specs invision spits out aren't helpful. If you are developing with a framework like React or Angular, and use a CSS preprocessor like SASS, then you have to rework everything invision gives you. It would be far easier if my designer would just email me a list of hex codes and some basic rules for font sizing and whitespace.
- daleco 8y ago
  The basic rules should be documented in the style guide, design system, and/or libraries. What would be interesting is to bridge the gap between the Invision Specs and what you expect. Indeed, I ran a survey on 8 devs, and I've been monitoring how they typically use it over the years (Invision, Zeplin, basic screenshot hosting...). Some Devs won't use the specs at all, sometimes delivering something off. Others, love it since it will reduce the back and forth during audits. You're right, specs will only be usefull to provide the dimensions and colors. However, this part is automated on the UX side, it prevents us from writing it down, which would be a waste of time: Mockups always change, we'd have to manually update the said specs so many times... This wouldn't scale well.

by daleco 8y ago

jbob2000 8y ago

I am happy that you found some use for it. Have you asked your devs how they use it? I do understand that mockups aren't just for developers, but you might be going to all that expense and effort for nothing. When I joined my team, after 6 months the designers asked me for some feedback on how I was using invision and I said it's just a screenshot host and they were shocked. But all the design specs are in there!. Yeah great, I know what 3em padding and 16pt font looks like, I'm not spending 2 hours poking through a clunky web app to find that out. The CSS specs invision spits out aren't helpful. If you are developing with a framework like React or Angular, and use a CSS preprocessor like SASS, then you have to rework everything invision gives you. It would be far easier if my designer would just email me a list of hex codes and some basic rules for font sizing and whitespace.

daleco 8y ago
The basic rules should be documented in the style guide, design system, and/or libraries. What would be interesting is to bridge the gap between the Invision Specs and what you expect. Indeed, I ran a survey on 8 devs, and I've been monitoring how they typically use it over the years (Invision, Zeplin, basic screenshot hosting...). Some Devs won't use the specs at all, sometimes delivering something off. Others, love it since it will reduce the back and forth during audits. You're right, specs will only be usefull to provide the dimensions and colors. However, this part is automated on the UX side, it prevents us from writing it down, which would be a waste of time: Mockups always change, we'd have to manually update the said specs so many times... This wouldn't scale well.