Settings and activity
2 results found
-
3,611 votesfeature-under-review · 412 comments · Adobe XD: Feature Requests (Read-Only) » 05 : Asset exporting · Admin →
An error occurred while saving the comment -
163 votes
Anonymous
supported this idea
·
It's like when you mow your yard or paint, you need some overlap so that the work gets done. That's all we want with export features. There's a gap here that I assume typically no one wants to do.
My assumption of the problem that needs a solution is if a designer starts to code, he's not going to stay a designer, or even a front end developer, he is going to want to be a back-end developer. Front end developers aren't paid enough to stay front end developers for all the learning that goes into being a coder. Is there a developer out there who just wants to be a front end developer only? Maybe if your paid well and comfortable at a large company, but I'm sure you want to learn the back end, right?
As a designer as part of a workflow, I want control to have the design implemented the way I want it, but with room for the developer to change things so that it functions.
In Xd (or in a companion app, or plugin) I'd care about translating to html, CSS, Javascript - Navigation, deciding between modals or all new pages, responsive sizes, Animation, transitions, the look, the layout, the UI components attributes and animations.
I don't care if I drew up a map that eventually was a real google map. Who cares if placeholder elements get thrown away. I want an empty shell that can be wired up. If graphics and pages need to be thrown away to make way for the real google map, system response, I don't really care. Just export my shell that includes these things, and let the developers delete what they want, wire up what they do want, and use the rest as placeholder.