136 results found

1. Export assets from design specs (we need a better way)

   There needs to be a better way or an alternative way to download assets from the design specs for developers. Right now, you would have to set each asset on each page to be able to be downloaded. This works great for a single page, but when you have a ton of pages representing either different states or different parts of the flow, it's hard to remember or even know which page you can download which asset from.

   Most assets that get used are made into symbols, so it would be great to be able to set the symbols to be "exported" so that from the design specs link, you could see a pool of all of the assets that can be downloaded instead of navigating to every page to see what they can even download.

   There needs to be a better way or an alternative way to download assets from the design specs for developers. Right now, you would have to set each asset on each page to be able to be downloaded. This works great for a single page, but when you have a ton of pages representing either different states or different parts of the flow, it's hard to remember or even know which page you can download which asset from.

   Most assets that get used are made into symbols, so it would be great to be able to set the symbols to… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

2. One dashboard for developers

   One dashboard with al prototypes for developers. Select project and see al specs. (zeplin) Now it's only send a link to developer.

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

3. Ability to view guides in Design Specs

   This is extremely important, almost as important as bringing back the old Design Specs flow which you took away for no logical reason.

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

4. Adding/Editing class names to Design Specs

   Ability to add/edit the class name to elements for developers.

   Possible Solution
   - Adding the ability to show layer name. Therefore I can write out the class name.
   - Adding Dev notes for designers to add additional information to design specs. This help developers drive better consistence for end product if using an existing design system.

   •  

   •  

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   4 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

5. Separate page to view all downloadable assets in Design Specs

   Edited: I'd like to see all downloadable assets in Design Specs, because sometimes I have assets that are repeated across multiple artboards.

   Original: It's possible to see all assets in all artboards in one click

   •  

   •  

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   4 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →
   AdminElaine (Adobe) (Product Manager, Adobe) responded

   Edited for clarity. Thanks for the update!

6. Export artboard to JPG/GIF/PNG/PDF from design specs

   Developers should have option to export art board from Design Specs to image, single or all art board.

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

7. Select platform in Design Specs on the web, not on publish

   I see that now the design specs allows the developers to extract design assets. Totally cool! Good job!

   One problem is that right now I have to mark my design spec specifically for one platform (ios, android or web). But sometimes we designers club those in one single file as separate group of artboards for simplicity. In such situations this feature is a problem. Both android and ios developers are using the same design spec, but only one of them can extract the assets.

   I would suggest to remove the platform selection option while publishing and provide platform selection to the developers after they’ve selected one or more assets from the design spec on the web.

   I see that now the design specs allows the developers to extract design assets. Totally cool! Good job!

   One problem is that right now I have to mark my design spec specifically for one platform (ios, android or web). But sometimes we designers club those in one single file as separate group of artboards for simplicity. In such situations this feature is a problem. Both android and ios developers are using the same design spec, but only one of them can extract the assets.

   I would suggest to remove the platform selection option while publishing and provide platform selection to… more

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

8. Overview of styles for entire Design Spec

   It is not easy to manage all the colors and styles in a design in XD

   There is no overall design specs for all artboards in the design specs nor in XD, making it hard to review all design styles in 1 place.
   Colors and Character Styles in assets can't be use as style guide/ in app design specs, the current version is not favoring this function

   Something similar to this suggestion is needed but with more function
   https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/34285129-integrate-designs-specs-inside-adobexd

   [Second feature request moved to: https://adobexd.uservoice.com/forums/353007/suggestions/34705201]

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →
   AdminElaine (Adobe) (Product Manager, Adobe) responded

   Thanks for your feedback! I’m going to keep this one open for the Design Specs feature, and have split out the 1 click one to this link, which you should upvote: https://adobexd.uservoice.com/forums/353007/suggestions/34705201

   In the future, please do file your ideas in individual tickets so that we can better aggregate with others who have similar ideas. Thanks!

   -Elaine

9. Display document name in Design Spec

   We need file name info in specs links to prototype.

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

10. With Copy SVG Code, linear-gradient is not unique

    If you have two things on a page that both have gradients in the background (see attached screenshot), the gradient for the first thing will be used on both. I did some testing and it looks like the ID on <linearGradient> and the fill="url(#linear-gradient)" on <rect> is the problem. If you change the "linear-gradient" on the second svg to "linear-gradient2", it fixes the problem.

    Can you change the "Copy SVG Code" functionality to make that "linear-gradient" value unique, like you did with stuff like "Group16" and "Rectangle5"?

    Example code:

    <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="200" height="200" viewBox="0 0 200 200">
    <defs>
    <linearGradient id="linear-gradient" x1="-0.804" y1="-0.902" x2="1" y2="1.11" gradientUnits="objectBoundingBox">
    <stop offset="0" stop-color="#b13393"/>
    <stop offset="1" stop-color="#149bd7"/>
    </linearGradient>
    </defs>
    <g id="Group_16" data-name="Group 16" transform="translate(-399 -372)">
    <rect id="Rectangle_5" data-name="Rectangle 5" width="200" height="200" rx="10" transform="translate(399 372)" opacity="0.996" fill="url(#linear-gradient)"/>
    <text id="Yes" transform="translate(454 496)" fill="#fff" font-size="57" font-family="Arboria-Bold, Arboria" font-weight="700"><tspan x="0" y="0">Yes</tspan></text>
    </g>
    </svg>

    <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="200" height="200" viewBox="0 0 200 200">
    <defs>
    <linearGradient id="linear-gradient" x1="0.089" y1="-0.051" x2="2.046" y2="2.011" gradientUnits="objectBoundingBox">
    <stop offset="0" stop-color="#b13393"/>
    <stop offset="1" stop-color="#149bd7"/>
    </linearGradient>
    </defs>
    <g id="Group_17" data-name="Group 17" transform="translate(-715 -372)">
    <rect id="Rectangle_29" data-name="Rectangle 29" width="200" height="200" rx="10" transform="translate(715 372)" opacity="0.999" fill="url(#linear-gradient)"/>
    <text id="No" transform="translate(778 496)" fill="#fff" font-size="57" font-family="Arboria-Bold, Arboria" font-weight="700"><tspan x="0" y="0">No</tspan></text>
    </g>
    </svg>

    If you have two things on a page that both have gradients in the background (see attached screenshot), the gradient for the first thing will be used on both. I did some testing and it looks like the ID on <linearGradient> and the fill="url(#linear-gradient)" on <rect> is the problem. If you change the "linear-gradient" on the second svg to "linear-gradient2", it fixes the problem.

    Can you change the "Copy SVG Code" functionality to make that "linear-gradient" value unique, like you did with stuff like "Group16" and "Rectangle5"?

    Example code:

    <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="200" height="200" viewBox="0 0 200 200">… more

    •  

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

11. Read-only mode on cloud documents for developers

    How about a free developer app? The current web developer handoff is already outdated. Due to Windows support, feature development is nonesistant. There have been few big feature updates since 2017. For designers it's fast and great. For everyone who works for designers, not so much.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  10: Developer Handoff  ·  Delete…  ·  Admin →
    feature-needs-more-info  ·  AdminElaine (Adobe) (Product Manager, Adobe) responded

    Thanks for your feedback. We’re constantly working on the web developer handoff surface, and it’s had some significant updates in the past couple of years. What do you specifically think you’re missing?

    By the way, we do have a large number of Windows users, so we do not intend to stop development on that platform.

12. Display component names in development prototype

    When you develop a design system in XD the structure of your components should be visible in the specs panel of your development prototype.
    If you build sensible components in XD with a clear naming scheme you can communicate a lot of context to the developer.
    In order to collaborate effectively teams should aim to share class or tag names between prototype and frontend code.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

13. Copy/export all colours from assets as Hex, RGBA, HSLA

    It would be very useful to be able to grab all the colour values as text in one go.
    To copy and paste into our SCSS or CSS.

    Could be a download or copy all.

    The shared assets in the Share for Development web pages are great. When it comes to the Colors, currently we can grab the Hex, RGBA, HSLA colours one at a time. I frequently want to grab all the colours.

    Code editors help designers see the colours, we don't need to do the colours one at a time to know which is which.

    •  

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

14. Rectangular Marquee Measurement Tool

    A tool that allowed me to make rectanular measurements would be useful. It could behave like the selecting marquee tools in PS.
    
    https://helpx.adobe.com/photoshop/using/selecting-marquee-tools.html

    This would be valuable because it would quickly give more specs to parts of the mockup that are not always XD elements. For example, if there was part of a mockup that was a screenshot, the XD measurement tools are not as accurate. Also is helpful for finding sizes of invisible containers. This would allow developers to freely grab measurements quickly for anything on the page.

    Thank you!

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

15. Show pasteboard text in design specs

    When I publish design specs (Share - Share for development) the text that I have outside art boards gets excluded. I have text to label different sections in the userflow, like headlines. When I share the same files for collaboration (Share - Invite to edit) the text is included. It would be nice if the text outside the art boards could be included in design specs as well, that way the developers can get the same information and understand the userflow.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

16. Define artboard order in the Design Spec using the Z-order of the artboards

    The artboards order should be determined by the order of artboards In the XD app, complex setups and groupings do not work well with the automatic
    left to right , top to bottom approach. It works well for simple setups

    Not ones that include 30+ pages, this approach causes more problems then the time it attempts to save

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

17. ink tool

    I would like to be able to ink (freehand draw using my wacom/other pen) my concepts and annotations.

    I know that there are some good work arounds like https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/20399002-workaround-for-annotations-in-design-and-preview-m but inking with arrows would be faster and more useful for me.

    I also know that some touch / pen features were implemented in https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/17431225-pen-and-touch-support-in-windows-10 but this is a specific extra tool using pen.

    The tool could be used to draw directly on the artboard, or on a toggle-able annotation layer per artboard.
    The inking could extend outside the artboard as necessary but would be associated with the artboard as part of the design spec.
    You should be able to choose to show the annotations layer when in preview mode.
    When publishing design specs, you should be able to see the annotations layer which is able to be toggled like in the app.

    I would like to be able to ink (freehand draw using my wacom/other pen) my concepts and annotations.

    I know that there are some good work arounds like https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/20399002-workaround-for-annotations-in-design-and-preview-m but inking with arrows would be faster and more useful for me.

    I also know that some touch / pen features were implemented in https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/17431225-pen-and-touch-support-in-windows-10 but this is a specific extra tool using pen.

    The tool could be used to draw directly on the artboard, or on a toggle-able annotation layer per artboard.
    The inking could extend outside the artboard as necessary but would be associated with the artboard as part… more

    •  

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

18. Design Spec Mode selecting inline multiple fonts, symbols or elements

    If I use a symbol font like Font Awesome and paste that into a text box with another font for my regular paragraph copy, my developers can't isolate and get the CSS, Fonts, Colors, etc. from the inline symbols or separate fonts. Would be nice to have a way to select a text container and toggle through the different fonts represented. Or click again to select a specific symbol or element in the text area and target that for getting specs on.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

19. Make truncated areas more accessible in design specs

    Currently, there is no way for the development team to be able to read the entirety of the truncated text. Please make this more accessible.

    This is happening on published links:

    1. In the "Search" results in grid mode.
    2. In the specs for Component name & Layer names

    •  

    •  

    •  

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  10: Developer Handoff  ·  Delete…  ·  Admin →

20. Show full layer name in design specs without ellipsis or add tooltip

    In the design specs that can be viewed in a web browser, if you open the specs panel an click on an element in the artboard, the specs panel will show the name of the selected layer.

    Problem is, if the layer name is a little longer, it gets cropped with "..." ellipsis and there is no way to see the full layer name. (See screenshot: Our layer name "GENERAL.HEADER.HELP-BUTTON.LABEL" is shortened to "GENERAL.HEADER.HELP-BUTTO...")

    Please either change the layout so that the full layer name is displayed.

    Or, as a really simple quick fix, add a title attribute to that <span> so that the full layer name can be seen in a mouseover tooltip. (This "feature" could be added with minimal effort.)

    (Use case: We are trying to use layer names for text elements to communicate translation IDs to developers and these are often longer than what visibly fits in the specs panel. But regardless of the use case, it's just good practise to add a way to show the full text for cropped texts.)

    In the design specs that can be viewed in a web browser, if you open the specs panel an click on an element in the artboard, the specs panel will show the name of the selected layer.

    Problem is, if the layer name is a little longer, it gets cropped with "..." ellipsis and there is no way to see the full layer name. (See screenshot: Our layer name "GENERAL.HEADER.HELP-BUTTON.LABEL" is shortened to "GENERAL.HEADER.HELP-BUTTO...")

    Please either change the layout so that the full layer name is displayed.

    Or, as a really simple quick fix, add a title attribute to that… more

    •  

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  10: Developer Handoff  ·  Delete…  ·  Admin →