Request details

Add Interactive Native Widgets/Controls to Prototypes

Support for native device functions (e.g. Cordova).

Example dropdown selection, media players, maps, etc.

This would increase the demo's effectiveness and allow for a more real-world prototype.

358 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)

We’ll send you updates on this idea

Peter DiBartolo shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • Edgard commented  ·   ·  Flag as inappropriate

    I need add a UIDatePicker on a Adobe XD prototype some body can help me?

  • Pete Conway commented  ·   ·  Flag as inappropriate

    When testing prototypes with end users we have a limitation in that we can't allow them to input text and it breaks the illusion when they have to, for example, tap a search box which will immediately populate or hyperlink to another screen. It would be great to be able to allow them to enter values (e.g. string, date, check box, radio group, toggle). This is particularly important when doing A-B testing between a working website and a prototype - it breaks up the user flow and forces the observer to step in to explain. It can also affect the interaction of the user as it can become confusing and unexpected, and it may colour their feedback if they can clearly tell which is the prototype and which is the original. In it is possible to enter data which makes it very compelling and it is currently appealing as an alternative to Xd.

    Another user has proposed a similar feature where alternative actions occur based upon data entered - whilst this would be nice it seems pretty complex and perhaps more than is necessary in the first instance. Perhaps a simpler model would be to allow a component to inherit the data value of another component, so that data entered on the first artboard is replicated on the second - these components would effectively be tied in terms of data but would be represented very differently visually.

    Maybe an approach for this could be:

    Phase 1 - add a component library which allows for data entry
    Phase 2 - allow for captured data to be tied to a elements across other artboards (e.g. I login with a user name and this can then be displayed on a subsequent screen, or a search string can be left in the search box on a subsequent artboard).
    Phase 3 - allow for conditional links between artboards based on selections

  • Cody King commented  ·   ·  Flag as inappropriate

    Please build a keyboard that when a user types it inputs text into the desired input field. This would be sick.

  • AdminPeter Flynn (Software Engineer, Adobe) commented  ·   ·  Flag as inappropriate

    Note: we're interpreting this request as focused on controls with standard/default native behavior. If you're looking for the ability to create interactive controls with *completely custom* behavior, please upvote

    If you want to use the state of widgets such as form inputs to affect the behavior of interactions in your prototype, please upvote

  • Anonymous commented  ·   ·  Flag as inappropriate


    * Calendar widget with hover capabilities ( For any kind of service)
    * Hover Capabilities for current selections



    *Log in Input (Email+Password)
    *Reminder request (email or text message)
    *Custom countdown widget (timer)
    *Video widget
    *Slider widget
    *Editable music player ( with option to upload one wav file maybe expandable?)
    *Contact form widget (editable)
    *GPS Locator
    *Interactive map
    *Importing files from Adobe Edge ( would be awesome!)

  • Wes King commented  ·   ·  Flag as inappropriate

    Perhaps the one major missing thing in XD for my use. Obviously a corresponding library of widgets, an enhanced UI Kit if you will, would be a necessity as well; not sure I want to be scripting or logic-enabling my own UI elements with "from scratch" designs.

  • Gideon Carstens commented  ·   ·  Flag as inappropriate

    Happy it's in the backlog because without this the product is still pretty much the same as Sketch. Really need 'real' components to run proper user tests.

  • Emasoft commented  ·   ·  Flag as inappropriate

    Add mobile keyboards interactive elements to allow user input of text, possibly both iOS and Android versions.
    With automatic "SLIDE UP" of the screen to avoid covering the text input field.

  • Anil Kumar commented  ·   ·  Flag as inappropriate

    Please support logic using operators (<, >, =, !=, etc) for displaying content.

    E.g. Disabling the Buy Button when their are zero items in the cart.

  • Brandon commented  ·   ·  Flag as inappropriate

    I agree that items such as dropdowns and buttons would help streamline the creation of the prototypes.

  • Nate commented  ·   ·  Flag as inappropriate

    I need the ability to have controls within an interactive prototype. By controls, I mean things like (radio buttons, checkboxes, toggle switches, dropdowns,, etc) that allow me to introduce more functionality into a prototype beyond a click-through style prototype.

    Having these controls setup as reusable symbols will allow me to maintain consistency and more easily manage them during the design process.

    Additionally, these would assist in setting a foundation for providing conditional logic to the prototyping functionality. If the checkbox is "checked" go to "Artboard 2". If the checkbox is "unchecked" go to "Artboard 3". The conditional logic could be more granular than just providing the ability to go to a different page but I wanted to provide an example.

  • Paul Mackinnon commented  ·   ·  Flag as inappropriate

    Should have various standard user input elements such as textfields multi-line), textbox (single line), various types of multi-select, checkbox, switch, date-picker etc. These might vary by UI kit for platform - iOS, Android, Web. Would allow customised widgets to same effect.
    When in prototype mode, clicking on a textfield would bring up the appropriate screen keyboard (on mobile simulation) or the actual platform keyboard where tested on device
    Since these input widgets can vary by platform, maybe a plug-in or libraries means to add new sets - or to allow customised widgets to be made and shared either with your team or open source to everyone in community.
    The simulation might allow selection of platform, or even some custom settings for example you get custom keyboards on devices by iOS extensions, etc. So the plug-in might allow a keyboard filled with emoticons for example, and it would be testable in simulation, as well as on device

  • Mansoor commented  ·   ·  Flag as inappropriate

    If you guys bring widgets to this amazingly design XD .

    Adobe just nailed it. its one the most easy to use and very powerful software.

    Please please please next release should be widgets.
    i think if you guys release a web version of it. thats very much needed for now. but i want to adobe to kick inVisions A**. or any other junk thats out there like sketch.

    Long Live Adobe

Feedback and Knowledge Base