Interactive Prototyping for User Testing
I use JustInMind to prototype Web and Mobile apps that I then user-test. The JIM application is less than optimal, but to attract a broader Human Factors / Usability / Design audience you're going to need a lot more than "scrolling."
Interactive elements such as text fields, check boxes, drop-downs, etc. that can all be connected, responding to user inputs as needed, in a manner that replicates a real application in its native environment is what is needed.
I look forward to that day, as your design tools and simple, visual linking paradigm are certainly winners.
Agree. Stuck with Axure mainly due to this.
Jonathan Fontanez commented
I'm an XD plug-in developer and this actually doesn't seem far off from what I'm working on. I've been focused on letting you apply you design though to an existing web app.
I'd be interested if this solves the problem you're thinking about, feel free to email me directly email@example.com
Fabio Barreiro commented
A must! I would get much better results when running test labs using my prototypes. Being able to simulate a real app would be dope
Axure prototyping is stil necessary in my workflow because of this. Please help me streamline my workflow by implementing these features.
Please implement this feature, Adobe!
This would be so useful!
JIM is a great example of using an advanced prototype tool for none developers too, as it shows in a side windows the elements in the artwork you are referring to. This way, you don't need to rely on your memory and see which element you are working on.
Can't wait to see your advanced prototype abilities. Good Luck :)
manu schwendener commented
[should these votes be merged with https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/12869229-animate-individual-elements-separately-custom-ani ?]
Paul Fournier-Carey commented
100% must have. How can we prototype & test without real interaction, animation/transition. Click through slide shows which animate the whole screen is just not enough.
Melanie Adelt commented
I am totally agree. Prototyping means interactive behavior from all elements like buttons-aktive, dropdown-swipe out or navigation scrolling without a seperate artboard ect.
When both: wireframing AND real protoyping is possible, so XD rules the world ;)
I NEED this. Interactive text fields would be amazing. If a user had the ability to type in a text box *during the test*, it would add to the realness of the test.
Wayne Hall commented
This is a must for me.
I work on prototypes for mobile, web and TV interfaces and for the TV interfaces it is critical that I can perform transitions using keyboard input. I use hardware to map a remote control to keyboard input which the user then controls the prototype with. The likes of Axure already support this.
Doesn't need to be complicated, just allow me to chose what action begins a transition, be it a click or keyboard input.
I agree. Axure has this but it's super clunky, it's called dynamic panels. The reason it's clunky is because it isolates you inside a specific view instead of having an artboard flow which is easier to keep track of.
If you manage to add interactivity to this product with your current artboard workflow, it will be a game changer.
totally agree! basic web components: interactive radiobuttons, checkboxes, select lists etc. and with trigger+action functionality.
Look at Axure, please.
Forget Sketch or Invision. I can do images with hotspots with Illustrator and Dreamweaver...
Full transactional websites (AKA "the real big companies" that paid for their apps) have all their "sugar" in screens with forms elements and some interaction logic (eg: conditional fields).
Please, consider this feature as a priority feature.
Strongly agree, although the design side is missing some key features (like gradients, etc..) the prototyping side is in it's infancy stage. Currently all I can do for web apps is basically show "slides" of an interaction.. which I was already doing in photoshop.
Anil Kumar commented
Please support logic using operators (<, >, =, !=, etc) for displaying content.
E.g. Disabling the Buy Button when their are zero items in the cart.
Nicholas McClay commented
Definitely agree, for usability testing being able to mock inputs/checkboxs/toggles etc is critical to evaluating the design.