Settings and activity

This feature makes sense only when using XD app to view or test prototype e.i. live font view. Any web-based URL prototypes do not have live fonts (because fonts are converted to images upon Share), thus a browser view in this description is not relevant.

When testing mobile app, it's best doing so in XD app, which looks and feels as native app unlike a prototype URL viewed in a browser. When opening XD cloud document in the app – it previews LIVE FONTS, however if your fonts are unique, they will not load correctly and get replaced with some default font, messing up layouts and UI (see attached).
I suggest Adobe a feature –
to map document fonts to a selected alternative from Adobe collection or other available online to load automatically.

Our Research often tests mobile app using a third party interface, which adds UI elements on top of the XD prototype often blocking content and confusing users, and disrupting their ability to flow through the tasks.

Ideally, I wish Adobe creating a feature available to subscribe in XD app to:
1. Direct user tasks and provide questionary
2. Record responses of user on-screen interactions (video-recording) and voice narration (audio-recording)
3. Time each task completion user-flow (timer)
4. Upload these recordings and artifacts to a designated research cloud

I ran into a problem with brand fonts when using XD app, which offers live fonts view vs an URL prototype. This issue could be solved by:

1. replacing all font-faces in bulk to those available online for live preview - exp. Univers faces changed (in bulk) to Roboto in the XD document on the cloud.

2. Original XD document font-faces are mapped to an alternative font-daces available online, enabling XD app to load them automatically instead of displaying an error.

Prototyping for mobile user testing is not simple due to variation of viewport sizes causing XD prototype screens cut off or displayed with odd margins. I wish Adobe can add some adaptivity of its prototypes to auto resize based on type of devices - such as phone, tablet, desktop.

I often need to present a scroll-triggered interaction/animation, e.g. app-bar and bottom-nav hide/show upon user scrolling the content.

This is a typical and essential behavior on mobile when user needs to view a long list of results, list of messages or emails or any list of long scrolling content thus to utilize screen real-estate to display more.

Having this feature be wonderful! With that I'd also like to have a capability to set a fixed position when scrolling (setting X and Y coordinates) of a certain element upon user scrolling.

I found out that creating a very simple live-looking loading event (spinner-wheel) is hard requiring multiple artboards to animate.

I wish to be able to build a self-time-animating component sitting on a single screen-artboard, while the artboard itself can be set to time-transition to another resulting artboard. (see attached)

Making a version of an existing Master-component would be very helpful for A/B testing and other cases when multiple versions of a similar design is required. E.g. a navigation bar with multiple interactive states when a current Master-component is still used across multiple documents and a new master needs to be tested. This will reduce redundancy of re-development of the same component and improve work efficiency.

The problem with using auto-animate that it does not behave naturally and does not let user to scroll back on.

I'm looking for a very common interaction pattern in mobile app experience – When user taps a button going to next screen (artboard), the BACK button (on the next artboard) should return to the previous art-board at the previously scrolled position.

I was wrestling with similar while looking for a very common interaction pattern on mobile apps. When user taps a button going to next screen (art-board) – BACK button (on the next artboard) should return to the previous art-board at the previously scrolled position. XD developers please pay attention to this!