Logan

My feedback

  1. 54 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    I mean, component states are XDs biggest differentiator. How can you not A) support them in your own library system, and B) not make them function cleanly enough for users to tell the difference between limitations and bugs?

    An error occurred while saving the comment
    Logan commented  · 

    Building a wireframing component library that my team can use across projects has become futile due to the lack of support for component states in CC libraries coupled with XDs inability to maintain nested component overrides from the master component into instances (is this a bug or a feature, I can't tell).

    I now have to tell my team to open the library file and copy/paste **only master components** that they need into their working file. Not exactly "at the speed of thought", XD. Seems like I'm actually devoting more and more thought to work-arounds for XDs limitations.

    Logan supported this idea  · 
  2. 10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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 →
    Logan supported this idea  · 
  3. 577 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Logan commented  · 

    Yeah this problem is compounded by the fact that there is no way to organize a file into pages like sketch does. I would essentially have to set up like 5 different files in order to separate different interactions into different links.

    I've noticed the usability problems in XD really compound pretty frequently. Too many to count honestly. After working with this or a couple months, I'm pretty upset that our organization has chosen to switch to XD. As it has slowed my workflow a LOT. The program is constantly fighting me, and I spend a lot of time having to come up with workarounds or redo work that shouldn't need to be redone.

    Need to edit a component? Forget about it, probably easier just to build a new one from scratch. Need to copy a component with overrides into another file because XD doesn't let you organize your file into pages? Forget about that too, your instance will revert to master state and you'll just have to make those adjustments all over again. States hardly carry over from file to file either (~30% success rate) assuming this is just due to bugs, but could be a feature, Who knows...

    I could go on and on...

Feedback and Knowledge Base