need

This is actually a really crucial part. As mobile UX dev you may can do something with XD at the moment but from a web dev. view, XD is far, far away to be used as a productional tool. I really would like to work with it but for now, I'm not using it anymore. It just makes no sense to me.

Echoing the below, I'm afraid. Using XD on a new project and found I can't scroll across to earlier artboards ...

This is crucial!

NEED!

ASAP!

I agree this is a huge need. For mobile it's a must to show user interactions. On the desktop I also think it's important to show clients how things flow down the page

Scrollable is a must for SaaS design with a lot of data to enter for one section on a web page, it needs to scroll down to capture all the required fields
Secondly new web designs are mostly now on one large scrollable length screen

Yes, Scrollable area is a must! otherwise I can't use it :(

Started an Xd prototype as well, but quickly found out about no scrolling or swiping, so Xd is of no use until that is introduced. Other features so far were very easy to use and quite nice, actually. Look forward to scrolling and swiping.

tried to start my first Xd prototype and dead in the water. Really would like this feature.

Just update my xd but still If I increase the artboard size, it doesn't make it scrollable when shared. It just makes the image taller, and zoomed way out. Looking forward for this feature to be fixed

Come on guys!! this feature is essential!!

YES PLEASE!!! TY, Love it so far.

How about Carousels too...for things like times/dates/ect?

If I increase the artboard size, it doesn't make it scrollable when shared. It just makes the image taller, and zoomed way out.

Can we have an response from Adobe on when we can expect this update to be available in XD as the product is becoming unusable if this feature is not implemented.

Thanks.

BIG UPVOTE for scrollable Artboards/areas as well as fixed headers/footers/navs.

IMPORTANT : elements inside a repeater group should have multiple "states". For example for a scrollable List, I should be able to have for each element a NORMAL state, a SELECTED state, an EXPANDED STATE and a COLLAPSED STATE. Otherwise if I expand or select a single item in a scrollable list with a repeater, all elements are going to change and expand/collpase. We need states for elements. And the user should be able to switch states in the prototype simulator with a special transition applied to a button inside each element. Something like "change element to state n.2". I've opened a feature request about this, go vote it.

A scroll area should not be the same as a repeater group. I can use a repeater group inside a scroll area only for the bottom half, for example. While the area at the top half is used by fixed content. Think about Facebook events page for example.

Important: in prototype mode the program should remember the exact scroll position of the last step, and position the scroll at the same coordinates. Otherwise simulating interactions inside elements of a list would be impossible.