We need a real solution that improves the design and development workflow. We need a tool that outlines all of the existing components and elements in a specific repository in a visual, drag and drop way. This would allow designers to pick and choose from the menu of existing components while making new designs. UXPin with Merge technology is a design tool that leverages dev tools through Git and Storybook integrations.
Sounds great, but what does that mean? First, we have Git integration. Merge allows you to import existing components from your Git repo into UXPin design editor. Second, we have an integration with Storybook , an open source UI development tool.
UXPin has built an integration with Storybook that allows you to use your existing design components directly in Storybook. This means you can use a library of your existing design components when building out your next UI changes. Then, you can just pass the design to a developer and have him use the code that he already has to build your new product.
This integration is currently only for the React framework, allowing you to pull in React components and work with them directly in UXPin. Your components will get stored in your UXPin design libraries, and any new components or updates will automatically sync into your library.
The functions of your components, and how they function, are also directly visible in your UXPin editor. This allows you to see mouse-overs, auto-fills, text field suggestions, emphasis animations and more directly in your UXPin editor. Everything that you design with UXPin Merge will be coded exactly to spec by your developers.
The UXPin storybook integration allows you to use your existing design components, imported from Storybook- public or private. As in Git integration, you can change properties and add new interactions to parts of the ready components if you want to. Designers use components that are already existing in order to do their design. If they need to change items, they know exactly which components to change, as well as every page that will be affected once that change is made.
Designers began to see the need to develop their own websites in order to give the proper attention to the details and complexities of their suddenly powerful and complicated interfaces. The outcome was a cost-effective pixel perfect website in less time. Going forward a little bit: Around we started to see how design and front end patterns united.
At the same time we also began to see front end techniques picking up proper, and significantly more sophisticated development methods. We also began to use tools like Grunt , Emmet and coffeescript , not to mention proficiency with the terminal became a requirement.
Each one of these — lets call them workflow enhancers — has a steep learning curve. Interfaces are getting more complex to design These days every designer must have their own arsenal of skills to deal with way more complicated interfaces then ever before.
I, myself, know how to code. But I find myself coding less and less, since I have major product design tasks of my own. We have to be far more versatile then before. So to sum it all up, I believe that to become a top notch designer one MUST know code to some extent , MUST be familiar with UX processes to some extent , MUST know how to communicate amazingly well with front-end devs, and MUST do product management to some extent , but most importantly — focus on improving and never compromise on design.
So… What do you think? We participate in the Amazon Services, LLC Associates program, and affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon. Articles Podcasts Menu. Knowing what is very different by knowing how. This takes us to the usual questions: do architects need to know how to build a skyscraper? Do car designers need to know how to build an engine? Do a movie director need to know how to act?
Does a surgeon need to know how to build a pacemaker? Of course not. But yes , they need to know what these things do. How they perform. What are their limits. And wonder what? A print designer that has never seen a type foundry will still be able to create wonderful prints. An industrial designer that has never seen a lathe will still be able to create wonderful objects.
It happens every day. Because how should a designer learn the limits of his media?
0コメント