plainclothes

My feedback

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Adobe XD: Feature Requests » 02 : Prototype mode  ·  Flag idea as inappropriate…  ·  Admin →
    plainclothes shared this idea  · 
  2. 63 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    25 comments  ·  Adobe XD: Feature Requests » Other  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    plainclothes commented  · 

    Save locally should, clearly, be the default.

    Save to Adobe's silly and unnecessary server system should be an opt-in preference.

    How about "check in to git repo"? That might actually be useful.

    plainclothes supported this idea  · 
  3. 26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    plainclothes supported this idea  · 
  4. 144 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    plainclothes supported this idea  · 
  5. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    plainclothes supported this idea  · 
    An error occurred while saving the comment
    plainclothes commented  · 

    This is closely related to actually finishing the basic cross-state inheritance as described in the issue below and elsewhere.
    https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/41922067-keep-elements-properties-between-states-propagate

    Once inheritance is solved in a useful way, the ability to opt elements out of inheritance would be a useful enhancement.

    As it stands, components are really just a dangerous distraction. For a project of any size and complexity, you'll be better off communicating states some other way until the XD team finishes this feature.

  6. 85 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    32 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    plainclothes supported this idea  · 
    An error occurred while saving the comment
    plainclothes commented  · 

    Wow -- that Flash reference brought back some painful memories!

  7. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    plainclothes shared this idea  · 
  8. 23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    plainclothes commented  · 

    This is a silly little thing. Why do I have to break the grouping of a component to unlink it from the master? Just disconnect / detach it and leave the grouping in place.

    plainclothes supported this idea  · 
  9. 130 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    28 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    plainclothes supported this idea  · 
  10. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    plainclothes commented  · 

    I need the ability to have more than one layout grid in my documents.

    Rather than setting one as the default, I should be able to define a grid, give it a name, then select it again from other boards.

    Ideally, these layout presets could be loaded into other documents as well (but higher order than a library asset).

    plainclothes supported this idea  · 
  11. 744 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    plainclothes commented  · 

    Just to clarify, there are two features needed here:

    1. Nested components can trigger a state change in the parent component
    2. One component can trigger a state change in another, unrelated component on the same artboard

    The super feature would be …
    A component can trigger an artboard transition *and* change the state of a component on that artboard.

    plainclothes supported this idea  · 
  12. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    plainclothes commented  · 

    My scenario is very similar to the OP's.

    To make XD even remotely usable, I have to break the app into separate flows. Even in this limited mode, a normal flow for me has 20-30 artboards. XD's flow upload is understandably slow, considering the number of interactions I usually am including.

    Even with only a couple of dozen artboards per flow or less, selective upload to the parent flow (as other apps have implemented) would be a big productivity boost for me.

    Related to the OP's last point, I might also have sections of a flow that aren't quite ready for my dev team. In those cases, I'll post a basic version first so they can see the whole flow, but I don't yet want to confuse them with enhancements that are still in-progress.

    plainclothes supported this idea  · 
  13. 105 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    plainclothes supported this idea  · 
  14. 1,024 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    plainclothes commented  · 

    This is the single most painful hole in the XD experience. I have 5 states on all my buttons and the app I'm working at the moment has a LOT of buttons. In many cases, those buttons also have a leading icon.

    Multiply this by five:
    1. Change the text
    2. Swap the icon component
    3. Recolor the icon component (because it forgets the color override)
    4. Resize the icon component (because it forgets the size override)
    5. Switch to the next state

    Component states are cool, but you pretty much hate them once you have a large app prototype up and running and you keep finding states you overlooked in your late night cram session.

    plainclothes supported this idea  · 
  15. 148 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    50 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →

    Sorry for the false alarm! Someone pointed out to me that I interpreted the request incorrectly. While you can now select objects both in the artboard and on the pasteboard, you cannot yet select objects on the pasteboard and complete artboards themselves.

    An error occurred while saving the comment
    plainclothes commented  · 

    The fixed pasteboard and lack of pages conspire to make this missing feature downright depressing.

    XD seems to be intended for messy designers who have no interest in efficiency.

    plainclothes supported this idea  · 
  16. 82 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    20 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    plainclothes supported this idea  · 
    An error occurred while saving the comment
    plainclothes commented  · 

    This is a big pain point for me.
    Here's my scenario.

    #1: I don't want your cloud
    I work with more than XD files (shocking, I know) and each of my projects is collected in a Git repo. I have no interest in throwing my files into Adobe's cloud, especially since it doesn't work with my other file types (code, Sketch, etc).

    #2: One doc doesn't have enough space for a serious app
    So I end up with multiple files to make room for all the features of the app. If XD had pages, like everybody else, I'd just build one mega file … but it doesn't. I usually end up with separate documents for each major feature area. For an app with pages, I often run up to 10 to 20 pages depending on the complexity of the app. With the pain and suffering of XD, I try to keep it to 5 documents or less.

    #3: I'm not always connected
    Sometimes I'll work from a trailer in the mountains. That's a pretty cool part of my job. But Adobe doesn't seem to think I should do that. In their eyes I'm connected or I'm not working. Okay then.

    All that to say …

    Linking to local documents as shared libraries is table stakes for this feature. Kano says, "Basic!"

  17. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    plainclothes commented  · 
  18. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    plainclothes commented  · 

    This would be hugely useful.

    If two long-standing feature gaps were addressed this could be done without a separate theme capability:
    - One component can be based on another, complete with states
    - Secondary states inherit default state changes

    Then you could quickly create a component based on the primary "theme", make a few style changes, and have everything else managed from the parent.

    plainclothes supported this idea  · 
  19. 22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    plainclothes supported this idea  · 
    An error occurred while saving the comment
    plainclothes commented  · 

    This is clearly a bug with the filter behavior.

    Because of multiple other issues with XD, I have to ungroup repeat grids to create variations.
    I inevitably make adjustments to what would have been grid items.
    The only efficient way to do this (short of fixing the repeat grid feature) is to filter my layer panel and multi-select the items to move.
    Of course, XD blocks me there too.

    I swear Adobe is trying to get me to convert all their users to Sketch.

    Just fix it. Seriously, how hard can this be?

  20. 421 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    plainclothes commented  · 

    I'd prefer to stack the panels … just like XD does on the right side … and every other design app has always done.

    XD needs a UX designer.

    plainclothes supported this idea  · 
← Previous 1

Feedback and Knowledge Base