Since you already started with scrollable area inside artboard, it would be awesome if we could define sticky header. For example, one page website has a lot of content, but I want to create sticky header so when I scroll down, it stays at the top. Maybe you could add the option so we can define the group and assign the sticky header option to it. That way on any artboard we can just assign that option to it and that's it.

Support for simple animation.
Example: Show/hide a slide or push menu

This would enhance a demo and engage prospects that are familar with common application patterns.

Define a scrollable area within an artboard

This provides real-world app use cases, such as a table, slideshow, or iOS dropdown lists.

Need Little bit tapping/hover effect on list/buttons/links during presentation to client. Its give an actual working product feel and help to make decision.

rollover, mouseover

Hi there, currently the only interaction is a page switch with some easing functions, but when you click a button, it would be nice that you van select a artboard that you can use as a "overlay" over another artboard. So that way you can create lightboxes in your protytype.

1. Ability to have a single object (or group) break out of its artboard and cross multiple artboards within a single prototype. The simplest use case is the creation of a global navigation bar that spans across multiple screens. This object's interactive elements would also work across multiple screens as well, and any edits to this object would update across the rest of the screens.

2. Easy interaction management and editing. Also provides consistency with consistent elements within an experience.

In order to full use this as a UX professional, I would have to have the ability to include gestures, most critically for handing a stakeholder a wireframe or design. Gestural swipes, two-finger zoom, force-touch, etc. Otherwise I don't think too many experience UX professionals will be able to properly communicate core functionality and the behavioral imperatives incumbent to the process.

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.

Ability to create and customise content carousels or slideshow type scrollable areas.

Currently there is a "scroll" feature in build, but it seems to be about page scroll and up/down scrollable areas.

The anchor link that target the specific part of the page. This is the significant user experience on web usability where user can "back to top" or can navigate (i.e. from menu bar) to the specific sessions without the need to scroll through entire pages.

It would be great with a few more features/interactive animations when you link the pages. More easing options. I guess what I'm saying I would like to have more animations and effects based on what we have on websites and apps to this date.

transition presets

For prototyping and user testing, a text input field control would be very helpful. Bonus if you could apply actions to enter / submit based on different strings.

Few more nice slide transitions wouldn't kill anyone, would it :)

Enable timed transition, something triggered by timing and not by user interactions (e.g. a notification from a server or a splash screen going away in a couple of seconds).

Support for native device functions (e.g. Cordova).

Example dropdown selection, media players, maps, etc.

This would increase the demo's effectiveness and allow for a more real-world prototype.

Please add the option to export all artboards of the prototype as a PDF document of many pages, preserving prototype interactivity saving links as PDF internal "pageTo" links (or invisible linkTo rectangles).
So that in this way the prototype can be navigated in the PDF file like on a web page (transitions excluded of course).
This would allow a very efficient "deliverable" design document for the client.

Now you can connect layers but what if you want to connect a hit area larger than a layer? Now you can work around this by drawing a rectangle behind the area and linking that up, but it would be great to be able to draw actual hotspots.

To be able to prototype for usability testing and demonstrations there needs to be a bit more intelligence around how experiences are joined up togehter.

If clause example:
If user makes choice a, do x. If user makes choice b, do z. And so on.

Variables:
When user makes a choice/clicks/fills in a field etc. assign a variable. Then allow designer to use variables in an if-clause to make decision which roots to go down.

Thank you :)

When previewing prototype need to be able to maintain page scroll position between screens to support interaction and animation behaviours (in Preview).