Matt D

My feedback

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

    We’ll send you updates on this idea

    Matt D supported this idea  · 
  2. 99 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Matt D supported this idea  · 
  3. 224 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    27 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Matt D supported this idea  · 
    Matt D commented  · 

    This feature would be great. Even if it was just like CanvasFlip Interaction Map ( https://blog.prototypr.io/tired-of-explaining-ux-flows-try-interaction-map-now-98a33cf9b4ef) with annotations on the interaction connectors, that would be such a helpful thing. Currently my workflow involves both XD + Lucidchart. XD just needs this high level view to be my all in one.

  4. 17 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Matt D supported this idea  · 
  5. 284 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Hi, all-

    “Convert to code” is fairly ambiguous, and I’m looking for more specifics as to what you’re hoping to get out of this. We already have a number of stories that go to specific technologies: HTML/CSS, XCode, Android Studio, etc. I’d like to close this one out in the interest of having more specific export paths.

    -Elaine

    Matt D commented  · 

    As one who codes, I am always concerned with page load, DRY, using preprocessors for HTML and CSS, using grid systems, scalability/refactorablity etc. I consider this the 'professional way' to build an application code base. For a Adobe or any other design application to be expected to do this for me via 'generating this type of source code' seems like a very unrealistic expectation therefore I am just fine with you guys focusing on more UX focused features such like video recorded user testing session. Basically, let's keep UX tools UX tools and coder tools coder tools.

  6. 241 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Matt D commented  · 

    I agree also with all the comments here. Currently I have pretty robust prototype built. The next step that would be absolutly fantastic to me would be to be able to email a bunch of test users with a specific task I want them to try to execute along with the link to the XD prototype. They click on the XD prototype link, and the session is recorded audio and screen so I can review the video of what they do to complete the task (a Think Out Loud user test) against the XD prototype. Maybe I get an email with a link to this video when the tester is done. The prototype in this case will probably need a start and stop feature for the tester but these things should be as non-invasive as possible to the actual XD prototype screen. This would allow us to ditch or extend much of our experiments we currently use Whatuserdo and Usertesting.com for.

    Matt D supported this idea  · 

Feedback and Knowledge Base