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! :)

Prototyping for people who are visual impaired is almost impossible to do. With the voice feature added it has become a bit easier to fake but if two more featured would be added Adobe XD could prototype for even more users.

• Vibrations could be added within the action area. This would make sure that extra feedback could be added to certain buttons/area's instead of textual feedback. This would also mean that two actions should be possible; a vibration and a transition if necessary.


• The VoiceOver function of iOS can't read the Adobe XD app. It doesn't distinguish buttons/area's that have an action attached to it, which makes it impossible to test with visually impaired users who use their iPhone with the VoiceOver function. No other prototyping tool can be read, would be amazing if the Adobe XD could in the future.

Would be great if XD would remember the last known component state when autoanimating to a new artboard. Or, better yet, let us mark components for state remembrance on artboard change. Otherwise we are right back to the thnig states was supposed to solve, duplicating artboards for the appearance of a saved state hahaha ;)

I have seen and voted on some other feature requests for conditional behavior, which could solve this issue too if implemented right, but this is a bit different.

I have posted an example prototype here:
https://xd.adobe.com/view/de27f8f1-15fe-4c5e-7a9b-deb283a7118f-a816/?fullscreen
pass: 4theXDteam

When the prototype launches, click the blue arrow(at the right of the screen) to collapse the panel, then click the large red map point(in the US), or the zoom icon on the navigator(top right panel). Notice how it reverts the panel back to it's open state, even though you had it closed when you transitioned to the next artboard. You can test this back and forth by clicking the zoomout/showall icon in the (top right panel) which will take you back to the first artboard.

Again, I could solve this with a bunch of duplicated screens containing all the different states, but then we're back where we started before states existed.

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.

Use (or have the option to use) a mouse-down (or touch-down) input to trigger changes instead of a full click (down+up).

When doing usability testing it's possible a user might try to click and drag something. Unnecessary confusion may result when the system doesn't respond at all (because a full click is necessary to trigger a change). If we could respond to the initial -press- or mouse-down we could provide an immediate response at the time the gesture begins, mitigating confusion.

Of course drag-and-drop would be super ideal, but the ability to respond to a press response would allow us to cope with this and other gesture limitations.