It would be of great value to be able to have error handeling this would create a more realistic prototype and scenarios for user testing.

Example 1:
If you add a text field and set it to an email field it should trigger an error when a user doesn't fill it in correct.

Example 2:
If you add a text field and set it to a mandatory field it should trigger an error when a user skips the field or presses a submit button.

At this moment there are no application I know of that have this feature and if they do have it, it's very complex to create. In example Axure.

I also feel that the focus is too much on mobile and this puts me of using this application. This is something that Adobe XD could focus on and make it an allround application rather than just focussing on smart phone.

since overlay feature released so why not to add a time for that overlay for instance when i click on CTA button overlay popup for specific time i define for 2 seconds then disappeared by itself.
that's like a toast in web design terms simple real life example for this in youtube when you like a video there's a toast/popup show in the bottom left of the screens tells you that you liked this video.
that's gonna be really cool for both website and mobile app to show you if your purchase has bee successfully done or your new settings save for instance.

OLD
second feature request is when the overlay show up the background turn to blur effect ... for clarifying the whole idea behind this it's very simple when overlay show up the page that overlay show in it turns to blur effect also would be awesome if i can specify the range of blur.

look attached files for more clarity.

*as a side note: i would put two different feature requests for both but since i see this two features very associated to each other i put it in one request.

I would expect the backspace key to remove transitions (in Prototype mode) instead of objects/layers.

Use case: In the Design mode the users adds & removes panels, afterwards he makes the switch from Design to Prototype mode. There his mindset is to create (and remove) transitions. He wants to modify the prototype and add/remove transitions. After selecting a (blue) transition, he presses the backspace key to remove an already existing transition, but as of XD v0.6.1.13 the layer/artboard where the transition originates from disappears.

What the backspace key is in Design mode (to undo one's action = removing an object), I would also expect it to be in Prototype mode (= to remove a transition).

Hi XD team!

I'm so excited that you are releasing the iOS and Android XD apps for testing on those devices. We have apps on those platforms, but I feel like the real game changer for us would be an OTT testing app such as a native tvML (tvOS) app for Apple TV that we could at least test our Apple TV app on.

We have our app on nearly every OTT platform you can imagine such as Apple TV Legacy and tvOS, Roku, Android TV, Fire TV, XBox 360 and new ones coming soon. Our stakeholders view our design comps on HDTVs here at our office.

The TV space is super hot right now and I ask that you explore the market for how much OTT app companies could really use a prototyping and testing solution.

Seeing our prototypes at full TV screen resolution could really help us make sure colors and fonts and image contrasts are working well.

Please be the first-to-market in this space! It could be huge for XD. Thanks! :)

It's a very good thing that we can now easily share colors between projects. But to be really useful, we need to change a linked color on a specific project.

I work on multiple projects based on the same UI library. Each projects has its own main color.

I created a project to maintain all my atomic elements and my other projects use those linked elements. But for now, when you use a linked color you can't change it on one project only so I can't use your great new feature for sharing assets between projects.

Here is how it could be implemented :

1. On the contextual menu of a linked color choose "Edit for this document"

2. Choose the new color

3. All the artboards and components with the first old color are updated with the new color

Complementary rule for linked assets updates : the unicity of a color is determine by its name and not its hexa code. So if a color has the same name in further projects, it has to be considered as the same color and not to be change by the update.