Pete Conway
My feedback
-
4 votesPete Conway
supported this idea
·
-
89 votes15 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
10 votesPete Conway
supported this idea
·
-
11 votesPete Conway
supported this idea
·
-
2,246 votesfeature-under-review · 573 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
2 votesbug-needs-more-info · 7 comments · Adobe XD: Bugs (Read-Only) · Flag idea as inappropriate… · Admin →Pete Conway
commented
I forgot to mention that the document was already one that had been saved at a previous point and it was saved on my computer, not as a cloud file.
Pete Conway
commented
I just had the same issue occur again and managed to get a screenshot of the error. It would be helpful if this could be addressed soon as I don't want to lose more work, and it is currently preventing me from doing what I would ideally like to be able to do with components
Pete Conway
shared this idea
·
-
1,338 votesfeature-started · 49 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
1,988 votes
We think you’re going to really, really dig the plugin integrations we’re making available later this year :)
Hoyle
Pete Conway
supported this idea
·
-
3 votesbug-investigation-in-progress · 9 comments · Adobe XD: Bugs (Read-Only) · Flag idea as inappropriate… · Admin →Pete Conway
shared this idea
·
-
517 votesfeature-under-review · 27 comments · Adobe XD: Feature Requests » 04 : Sharing on the web · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
1,311 votesfeature-started · 29 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
338 votesPete Conway
supported this idea
·
-
971 votesfeature-under-review · 65 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
6,987 votesfeature-started · 958 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Pete Conway
commented
I'm sure someone has already mentioned this but it would be useful if these could be triggered in different ways, e.g. trigger on click, trigger on page page open etc.
Pete Conway
supported this idea
·
-
22 votesPete Conway
supported this idea
·
-
384 votesfeature-in-the-backlog · 16 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Pete Conway
commented
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 Proto.io 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 selectionsPete Conway
supported this idea
·
-
1,813 votesfeature-under-review · 190 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
Carousel / Side-scroll / Horizontal Scroll
-
Screen Shot 2020-01-16 at 11.34.30 PM.png 868 KB -
Screen Shot 2019-11-13 at 2.53.05 PM.png 151 KB -
Screen Shot 2019-11-13 at 2.49.29 PM.png 594 KB -
ProtoPie.jpg 78 KB -
Horiz Scrolling.png 264 KB -
design.png 276 KB -
preview windows.png 265 KB -
preview.png 351 KB -
Screen_Shot_2018-04-24_at_5.16.08_PM.png 211 KB -
2-1-telaDescontos.png 220 KB -
Medium.gif 3339 KB -
AppleStore.gif 2212 KB -
AppStore.gif 2073 KB
4,558 votesfeature-under-review · 384 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
-
6,535 votes383 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
Reopening the feature request, based on feedback.
Pete Conway
supported this idea
·
-
5,978 votesfeature-started · 323 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Pete Conway
commented
Not sure if this has already been mentioned but horizontal scroll (for carousels etc.) would also be important as part of this
Pete Conway
supported this idea
·
.png){kind=link}
Firstly, I love the new component states - it's one of the best changes introduced in Xd for some time and is a game changer in terms reducing the numbers or artboards and clearing up user flows, so thanks and good job!
One of the problems I currently have though, is that if I work on a project and then move onto a different one where I need to tweak and rework some of the components I generally copy the file so that I can reuse components, but what I don't want is for the components in the new file to be forever linked to the fate of the first one if that makes sense?
There are some scenarios where this is useful, e.g. if you're building a site and have a fixed set of assets, but when building full fledged products and telling complex stories with prototypes, components are a great time saver for representing data flows and changes but I want to have freedom to use them and tweak them differently in different files.
It would be great to be able to re-base components within the new file, so the components would retain all their states etc. but I can make any changes in the new file, completely separately of the old.
I think this is the same feature as indicated in this issue, but you would need to confirm with the original poster: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/38355469-unlinking-components