It is very helpful to design a multi-layer menu. Say you have a menu that slides from the left (overlay #1) and then on click/hover action a second level menu appears (overlay #2). Currently we can't do this in XD.

Figma already has it... just migrated to them. Much better in many ways, and I didn't find a worse feature yet.

This needs to happen. I have not worked on a single website or app that does not require a feature similar to this one. An Advanced Filter with drop downs inside of it is one of the most requested things in todays market. Adobe you need to get this done.

Agree this would be fantastic! Nike (Just Do It) this ASAP!

Would be lovely...

We NEED this yesterday

Seriously... Adobe... DO IT! DO IT NOW!

Glad to see that this still hasn't been solved 😭Excuse me while I spend several hours doing a bunch of micro-interactions

Hey @XDTeam. How come you are not working on implementing nested overlays when it is:

- an open community request since 2018
- it's a crucial interaction in modern applications

You've seen this in many apps too. It's also baked in into iOS. For instance, here is an use case:

1. The user is on a screen where she triggers an overlay interaction (the screen slides in from the bottom)
2. The user clicks inside this overlay and triggers another slide in, the second overlay. This one might come again from the bottom, from top, doesn't matter.
3. Then the story continues for the third time and so on...

As it's well known, this is still not possible with XD. I think Figma does it and they call it "Overlay Swap", but I'm not an active Figma user.

Before someone comments this can be done with component states, that is unfortunately only true in limited scenarios because only auto animate ans dissolve transitions are supported between states. Overlay transitions are not supported.

Then there is a question of usability, while even if overlays could in future be achieved with component states it would be unpractical to overload components with so many states and so many possible scenarios of transition and inherited content.

Overlays belong on their own artboards. They behave in a way as components, where you call them up when they are needed. We just need a way to have multiple of them stack up on each other.

Please.

Yes, I need this feature to build my prototypes. It would be great if you can define an originate point from where all the following overlays will be started. Another option ist to move the overlayframe to the desired page.

Yes, it would be great to be able to swap an overlay so the overlay can have multiple states without having to create the overlay as a component.

Does any other prototype software allow that?

Yes! I have just wasted a bit of time trying to figure out why I couldn't overlay an overlay. Guess i'm going to need to manually create this interaction. Glad to see i'm not alone though - hopefully with a future update!

A must have feature. Didn't expect that XD doesn't have this feature. Let's hope it's going to be added this basic feature soon.

Thanks Nick for introducing this request.

Was thinking i was doing something wrong... I did not expect to not be able to do this.

I just wanted to do an overlay on top of an overlay without dismissing the first one (because it evokes the animation of the first overlay and only after that does it trigger the second overlay, which results in a weird behaviour)

Yes, overlays are unusable if you have more then a simple menu. Using multiple overlays is very glitchy and doesn't work well for micro-interactions. Or moving from a small overlay to a larger one doesn't work.

Yes please. Thank you!

Agreed... I am already doing this for a multi-tiered navigation structure idea I have, and it's working, but glitchy, and I have to create a lot of duplication to keep it from completely breaking. Also, even if you select none as your transition, you still get a flash as one overly replaces they other. Would be nice to at least have that replacement be seamless as a start.

I actually found this because I was in the process of writing this feature request myself ;)

This is a must have, otherwise what I am having to do is hack together detailed duplicate screens to make this work which is highly inefficient.

Complex systems interfaces just need this feature.