Forum for Adobe XD CC?

[r_tist]

Hi,

I am not seeing a forum for XD CC. Anyone know why? Also, does it not export HTML/CSS like Avocode, Invision or Sketch?

Was thinking to explore the application on my desktop since it comes with the suite of products. However, it requires Windows Anniversary Edition. Worked with my IT to do this, and I still see the incompatibility message in Adobe CC application mgr, even though Windows site states: You don’t have to do anything to get the Windows 10 Anniversary Update, it will roll out automatically to you through Windows Update if you’ve chosen to have updates installed automatically on your device.

Can anyone advise? Thank you.

[Jon Fritz · Accepted solution]

I know nothing about the program aside from the forum is over here: Adobe XD CC

[paulk7737514]

What does it do?

[osgood_]

paulk7737514  wrote

What does it do?

Its  a wire-framing application with some minimal dynamic bits. A waste of time really I think personally - If you're ok at coding you can produce something faster and more akin to the finished product directly in the web editor/browser, add a few media queries and it takes shape very quickly.

[Nancy OShea]

Adobe Experience Designer is aimed at UI/UX designers for wireframing & prototyping apps and then collaborating with other team members. 

Pre-2012 computer users need not apply.   XD needs modern computer hardware and software to run.

Adobe XD System requirements

Tutorials

Adobe XD tutorials | Learn how to use Adobe XD CC

Nancy

[rayek.elfin]

osgood_  wrote

paulk7737514   wrote

What does it do?

Its  a wire-framing application with some minimal dynamic bits. A waste of time really I think personally - If you're ok at coding you can produce something faster and more akin to the finished product directly in the web editor/browser, add a few media queries and it takes shape very quickly.

XD is one of those "too little, too late" Adobe efforts - at least in its current incarnation. More of a toy than anything else, and the competition is FIERCE - some very powerful and user-friendly prototyping software exists in the wild. And I wholeheartedly agree with you that generating html/css based prototypes is a better choice than XD.

The problem is that XD provides almost no interactivity at all. It is based on wireframing concepts, which are outdated by themselves. Nowadays the wireframe stage is absorbed into the prototyping phase in agile dev workflows. Wireframes are too static, too unwieldy in many cases.

[B i r n o u]

while being adept at agile development, and fast HTML prototyping, I do not especially share your views on the uselessness of a proptotyping application. I am invested in this analysis which consists of using a third application (graphic) to make pre-model of the various projects on which I work (not enough in any case) .

In general, the teams in which I participate are scattered in the other corners of the globe, involving various native languages ​​(generalized English, however), time slippage, plurality of profiles, completely heterogeneous work environment, collaborative and network work, etc.

many designers, architects, project managers, sponsors, clients, SEOs, accessibility specialists can not really work on bases that are not graphic, easy to use and quick to get started ...

however, we, developers, but before any generalist of building and creating the structure, integrating metadata, full designers of the relationship inter-language (structural, visual and interactive), ... we do need applications such as XD, Invision-app, Sketch, UX Flow and so on, to communicate and validate points ... but they always remain incomplete ...

they should not only present the idea, but they also allow us to work on

• the structure (labeling, id-ing and class-ing, tag-ing, grouping & nesting, block-ing...),
• setting sharable elements,
• getting and setting informations of graphic chart (colors, typos, sizes, proportionality),
• defining iconography (fonts, elements , logos, links ...),
• indicationg links and relation to various graphic applications (canvas, svg, png, psd, ...),
• binding data sources (xls, json, mongo, dbb ...),
• plugin ontology and metadata (structural and information ...),
• forking DataDriven management (RWD, Breakpoints, Accessibility, Printing, Web of Things ...)
• and so much more....

it would be nice to open such a debate ... don't you think ?... only in the sense of moving things forward and share ideas about prototyping in general ...

moreover it should not be forgotten that all the applications integrates necessarily in flows, themselves to be prototyped ...

in that case, visio, freemind are excellent tools at this level ... example of global application flow (https://www.screencast.com/t/zNdt0zRPu) and example stream type (https://www.screencast.com/t/m00U2C5uW) ... to this scheme, it lacks the application layer that would be located between the flow management tools and the prototyping tools ...

in short ... which screens, which displays, which layout ... when?

[osgood_]

https://forums.adobe.com/people/B+i+r+n+o+u  wrote

while being adept at agile development, and fast HTML prototyping, I do not especially share your views on the uselessness of a proptotyping application. I am invested in this analysis which consists of using a third application (graphic) to make pre-model of the various projects on which I work (not enough in any case) .

In general, the teams in which I participate are scattered in the other corners of the globe, involving various native languages (generalized English, however), time slippage, plurality of profiles, completely heterogeneous work environment, collaborative and network work, etc.

many designers, architects, project managers, sponsors, clients, SEOs, accessibility specialists can not really work on bases that are not graphic, easy to use and quick to get started ...

however, we, developers, but before any generalist of building and creating the structure, integrating metadata, full designers of the relationship inter-language (structural, visual and interactive), ... we do need applications such as XD, Invision-app, Sketch, UX Flow and so on, to communicate and validate points ... but they always remain incomplete ...

they should not only present the idea, but they also allow us to work on

• the structure (labeling, id-ing and class-ing, tag-ing, grouping & nesting, block-ing...),
• setting sharable elements,
• getting and setting informations of graphic chart (colors, typos, sizes, proportionality),
• defining iconography (fonts, elements , logos, links ...),
• indicationg links and relation to various graphic applications (canvas, svg, png, psd, ...),
• binding data sources (xls, json, mongo, dbb ...),
• plugin ontology and metadata (structural and information ...),
• forking DataDriven management (RWD, Breakpoints, Accessibility, Printing, Web of Things ...)
• and so much more....

it would be nice to open such a debate ... don't you think ?... only in the sense of moving things forward and share ideas about prototyping in general ...

moreover it should not be forgotten that all the applications integrates necessarily in flows, themselves to be prototyped ...

in that case, visio, freemind are excellent tools at this level ... example of global application flow (https://www.screencast.com/t/zNdt0zRPu) and example stream type (https://www.screencast.com/t/m00U2C5uW) ... to this scheme, it lacks the application layer that would be located between the flow management tools and the prototyping tools ...

in short ... which screens, which displays, which layout ... when?

Probably correct if you have no alternatives other than to work with others  in a team but for the small independent not essential. I've wasted enough of my life dealing with teams of incompetants and time wasters......I now just get on with the job and cut the bullcrap of which 99% of business is.........bliss.

Much like Bootstrap is only beneficial in a team environment, not because it's any good in terms of the coding it produces but because it allows a team to work in a unified workflow, that's if you want to be a robot.

Different strokes for different folks I guess......room for all. I can stand at  machine all day knocking out 100 pairs of 'plastic' shoes or sit at my workbench handcrafting a good pair of leather ones, taking pride in what I do.

[B i r n o u]

I must admit that I always have enough trouble understanding your positions ...

what I perceive in your answer ... in only three sentences ... is... three denigrations, or at least three very negative returns ... it almost looks like frustration ...

I quote

"... I was wasted enough of my life dealing with teams of incompetants and time wasters"
"... that's if you want to be a robot ..."
"... I can stand at machine all day knocking out 100 peers of 'plastic' shoes or sit at my workbench handcrafting a good pair of leather ones, taking pride in what I do ..."

I have not tried to attack anyone ... I have just tried to be constructive on what a real prototyping application can bring based on the projects I am invested in ... and I do not think that

- nor to work with incompetent people ... they are all very much on the contrary very captivating
- neither to work like a robot ... everything is calculated, analyzed in order to answer better to the real needs and to everybody aims
- and even less to do the slaughter .. everything is developed to measure in the final needs and aim... and that is why we are paid ...

so I still miss understand your points for being so negative... but I'm certainly missed your bottom line

[osgood_]

https://forums.adobe.com/people/B+i+r+n+o+u  wrote

so I still miss understand your points for being so negative... but I'm certainly missed your bottom line

You could view it as negative if you want, I view it as being realistic.

Once you've been there and done it you look at things from a very different persepective. The hours spent sitting around a table in a board room pretending you are important and are making important decisons, nothing much moves. You take 2 hours to explore and say something which can be said in 10 mins but business is about wasting time for many in positions of 'importance', its how they justify their existence. It doesnt fool me these days - cut the crap and just get on with the job.

I aliken the above to using wirefarming programs, you spend copious amounts of time doing something which could be done using a better/quicker workflow. Why do I want to spent time drawing out a desktop version, a tablet version and a smartphone version of a website on what is effectively a digital bit of paper when I can just use a few simple media queries in a 'real' html situation to achieve a better representation of the product.

The only real reason I can think of is is you are not a good coder and rely on something like Bootstrap, Foundtaion or Wordpress etc. I can imagine it could take sometime to iron out all the problems they will likely cause but if you are an good coder its just so simple to work directly within the web-editor/browser to produce a 'visual' these days.

I'm not sure that's negative just a different way of working. I used to layout all of my websites in Fireworks when we were in a static environment beacuse we used many images to create things which we would now not do with images. Its just as easy to draw a line or a box in html now as it is in an image-editing program. Coupled with the fact that there is a trend in how websites are laid out these days - a sort of holy grail to follow with a few tweaks.

As for frustration yeah hell I'm frustrated because I think many involved in web-development are over complicating what can be a simple process. Probably out of self gratification rather than sense prevailing.

[B i r n o u]

Why talking about wireframing program... XD, Sketch, Invison app are not wireframing program... but UI/UX prototyping program... which is for what I think far from being equal...

the subject is by the way XD CC ?

so, now why talking about Bootstrap, Foundation, Wordpress... ?

so, now why talking about being good (or bad) coders ?

we talk about prototyping.... pro... to... ty... ping arf arf...

[osgood_]

https://forums.adobe.com/people/B+i+r+n+o+u  wrote

Why talking about wireframing program... XD, Sketch, Invison app are not wireframing program... but UI/UX prototyping program... which is for what I think far from being equal...

the subject is by the way XD CC ?

so, now why talking about Bootstrap, Foundation, Wordpress... ?

so, now why talking about being good (or bad) coders ?

we talk about prototyping.... pro... to... ty... ping arf arf...

XD, Sketch are certainly used by many web-developers as wireframing applications.

I bring in other related subjects because its all integral to a workflow and may be a strong reason why one does something the way they do.

For instance perhaps a poor coder will not feel confident working directly within a web editor application so its easier to produce a wireframe in an image-editor initially. Perhaps a developer is not a designer and they feel more comfortable working on paper first. Perhaps those with a design background and are good coders feel at ease working directly within the web-editor/brower application.

[B i r n o u]

this time in your answer we understand better what you are talking about ... and this is more cordial, more moderate ...

you do not mention the incompetence of the teams, nor the poor quality of the mass productions, nor the recourse to javascript libraries which were not the subject, nor CMS ... by and large, neither do you drown the fish, nor you be thundering on parallel topics ... cool ...

[osgood_]

https://forums.adobe.com/people/B+i+r+n+o+u  wrote

this time in your answer we understand better what you are talking about ... and this is more cordial, more moderate ...

you do not mention the incompetence of the teams, nor the poor quality of the mass productions, nor the recourse to javascript libraries which were not the subject, nor CMS ... by and large, neither do you drown the fish, nor you be thundering on parallel topics ... cool ...

I'm glad you found it more to your liking.

[B i r n o u]

it's not that it's for my taste ... it's just that your comments have become relative to the subject, and formalized into something simply audible ...

[osgood_]

https://forums.adobe.com/people/B+i+r+n+o+u  wrote

it's not that it's for my taste ... it's just that your comments have become relative to the subject, and formalized into something simply audible ...

Comments were relative to the subject/s all along, not my fault you aren't able to marry them up beacause they are a bit 'creative' . Perhaps its a language translation issue as you seem to think I'm 'attacking' you personally when I respond to your opinions, which I can assure I'm not.

[rayek.elfin]

https://forums.adobe.com/people/B+i+r+n+o+u  wrote

while being adept at agile development, and fast HTML prototyping, I do not especially share your views on the uselessness of a proptotyping application. I am invested in this analysis which consists of using a third application (graphic) to make pre-model of the various projects on which I work (not enough in any case) .

In general, the teams in which I participate are scattered in the other corners of the globe, involving various native languages (generalized English, however), time slippage, plurality of profiles, completely heterogeneous work environment, collaborative and network work, etc.

many designers, architects, project managers, sponsors, clients, SEOs, accessibility specialists can not really work on bases that are not graphic, easy to use and quick to get started ...

however, we, developers, but before any generalist of building and creating the structure, integrating metadata, full designers of the relationship inter-language (structural, visual and interactive), ... we do need applications such as XD, Invision-app, Sketch, UX Flow and so on, to communicate and validate points ... but they always remain incomplete ...

they should not only present the idea, but they also allow us to work on

• the structure (labeling, id-ing and class-ing, tag-ing, grouping & nesting, block-ing...),
• setting sharable elements,
• getting and setting informations of graphic chart (colors, typos, sizes, proportionality),
• defining iconography (fonts, elements , logos, links ...),
• indicationg links and relation to various graphic applications (canvas, svg, png, psd, ...),
• binding data sources (xls, json, mongo, dbb ...),
• plugin ontology and metadata (structural and information ...),
• forking DataDriven management (RWD, Breakpoints, Accessibility, Printing, Web of Things ...)
• and so much more....

it would be nice to open such a debate ... don't you think ?... only in the sense of moving things forward and share ideas about prototyping in general ...

moreover it should not be forgotten that all the applications integrates necessarily in flows, themselves to be prototyped ...

in that case, visio, freemind are excellent tools at this level ... example of global application flow (https://www.screencast.com/t/zNdt0zRPu) and example stream type (https://www.screencast.com/t/m00U2C5uW) ... to this scheme, it lacks the application layer that would be located between the flow management tools and the prototyping tools ...

in short ... which screens, which displays, which layout ... when?

I completely agree with you! When working with teams and for user testing, prototyping is absolutely required. Don't misunderstand me: prototypes are essential. When I work on small game projects, for example, I always create small prototypes to figure out if the parts come together as a fun game or not.

What I am saying is that static wireframes have lost their usefulness for myself and teams I work with, and have been replaced years ago by working prototypes.

As far as prototyping software is concerned: I and the teams I work with use various tools. For quick website prototyping I really like Pinegrow at this point. We still use Axure, which allows for all sorts of scenarios, and other tools. It depends on the project at hand. I don't believe in a single prototyping tool which caters for everything.

When I compare Adobe XD to what is already available, it falls short on so many levels, I don't even know where to start. Merely the simple facts that it uses the hamburger icon and that the GUI is completely and utterly static and cannot be customized is breathtakingly inept; or that the highlighted tool icons are barely visibly selected - and XD is supposed to be a UX designer tool? Laughable. Stupendously inane. And that's merely the GUI of the app.

XD might be okay for wireframing and simple "click here to go there" interactions. For designers not used to more involved and capable prototyping apps it might look "cool". As far as I am concerned XD is the emperor who wears no clothes. Perhaps it will improve in the future, but where will the other apps be at that time? Competitors already offer SVG animations. And proper controlled asset export. Highly complex interactive scenarios for user testing sessions. And... And... And.. The list goes on, and on, and on.

My apologies to come down so hard on XD, but I just can't see its value for any UX designer. I guess it's "free" with the Adobe suite, and that's probably the reason why people clamor about it.

[B i r n o u]

Well; I think that we share more or less the same point of view... and if you check the require list for feature that a prototyping tool need to integrate none of those items are handle by XD...

the only place where wireframing was really interesting was to start from a digitalised paper draw and to merge it on a digital document... (Fw was great for it...) and currently, the second part where I still use wireframing is when I work with an architect of information to delineate screen surface occupations based on content strategy