Pete Conway
My feedback
-
167 votesfeature-started · 32 comments · Adobe XD: Feature Requests » 10: Developer Handoff · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Pete Conway
supported this idea
·
-
18 votesbug-needs-more-info · 13 comments · Adobe XD: Bugs (Read-Only) » System · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Pete Conway
commented
I've had the same problem. This latest release has been incredibly unstable for me and my colleagues. I regularly have issues saving, and am consistently having keyboard registration issues again. It's a realy shame - I'd much rather these ongoing stability issues were addressed before any more features are added to the application
-
6 votes
An error occurred while saving the comment Pete Conway
commented
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
Pete Conway
supported this idea
·
-
159 votes23 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
20 votesPete Conway
supported this idea
·
-
32 votesPete Conway
supported this idea
·
-
2,628 votesfeature-under-review · 635 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 →
An error occurred while saving the comment 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.
An error occurred while saving the comment 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,423 votesfeature-started · 50 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
2,060 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
·
-
568 votesfeature-under-review · 28 comments · Adobe XD: Feature Requests » 04 : Sharing on the web · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
1,377 votesfeature-started · 30 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
360 votesPete Conway
supported this idea
·
-
1,069 votesfeature-under-review · 67 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
7,792 votesfeature-started · 1062 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment 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
·
-
387 votesfeature-in-the-backlog · 16 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment 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
·
-
2,022 votesfeature-under-review · 198 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
Carousel / Side-scroll / Horizontal Scroll
-
Home_Init Browse_a1.png 276 KB -
2.png 836 KB -
__-___2x.png 603 KB -
dribbble___2.png 1481 KB -
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,839 votesfeature-under-review · 390 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Pete Conway
supported this idea
·
-
-
6,725 votes389 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
·
.png){kind=link}
I am stunned that this wasn't implemented along with the component states functionality right at the very beginning, and that there wasn't clear information about the fact that states could not be exported for development.
This is absolutely a business critical feature for us. I've been working on a large project for many months and have just been informed by our development team that they are unable to access the design specs of the different states of the components I've built. We have designed hundreds of screens using components, some of which have up to 9 or 10 different states, and to try and unravel this and change all the designs, files and flows to not use components, or to manually export each state would take weeks worth of effort.
I'd appreciate it if someone could get in touch to discuss this with me and let me know when the fix is due to be released as it will have a significant impact on our project timescales. If there is a quick alternative to getting the dev teams what they need in the meantime I'd be really grateful!