4 ms·
Seems to make sense to me. When I worked with designers the handover was often odd. I always thought "if he can draw up this whole thing in Zeplin, why doesn't
by lordnacho 10y ago
Seems to make sense to me. When I worked with designers the handover was often odd. I always thought "if he can draw up this whole thing in Zeplin, why doesn't he just give me an HTML doc that a coder can then generalize? And then you'd end up having to ask about a bunch of cases like mobile sizes.
There's also the problem of knowing what can be done in HTML/CSS/JS easily and what cannot. If the designer just made the page without the variable parts it would solve this issue. You don't need to know a hige amount about coding, just enough to make your page look the way you want, and to know when it can or cannot be done.
Of course everything that's at the interface between two roles can be argued to be on one side or the other.
- jasim 10y agoI'm building a tool that does exactly what you said -- it creates all the HTML and CSS from designs, saving immense amount of time doing the rote work of transcribing the designs into code. With design tools supporting reusable abstractions (Symbols in Sketch), we're even able to create reasonably factored React components straight from the designs. https://protoship.io/tools/uipad.html https://protoship.io/tools/uipad.html. There are quite a few challenges in this approach. We have to work with a static snapshot of the design and infer things like whether a container is auto-width (fit to content), a percentage of the parent, or fixed width container. Unifying multiple states of a component is another problem. Designers draw the same component multiple times to show different states (disabled, focussed, active etc.). The way we're approaching this is to identify the extra information required to take a static design into a responsive representation and ask the user to annotate it before generating the code.
- pavlov 10y agoYou're not the only one wondering why handover is so limited! I worked on React Studio, which is another tool that tries to solve this: https://reactstudio.com https://reactstudio.com It's a designer-oriented front-end tool. Three big features are responsive mobile device previews, easy creation of components, and data-driven design (e.g. filling out lists based on real data from a server or mockup data sheet). You can design in place, and there's also a Sketch plugin for easy import. The tool outputs very clean React+Webpack projects using Facebook's "create-react-app" toolchain, so the code is actually useful. Going the other way, developers can control and augment React Studio's output using plugins -- thanks to these hooks, it's actually more like a metaprogramming utility, a "design compiler", rather than just a WYSIWYG prototyping tool.
- woah 10y agoThe problem with these kind of tools is that as soon as the generated code has been modified, you can not bring it back into the visual tool.
- seanmcdirmid 10y agoWell, that's a problem that is being worked on, e.g. see https://www.microsoft.com/en-us/research/publication/its-alive-continuous-feedback-in-ui-programming/ https://www.microsoft.com/en-us/research/publication/its-ali... https://arxiv.org/abs/1507.02988?context=cs https://arxiv.org/abs/1507.02988?context=cs