I'm curious as to the size and composition of the QA team for the XD product. It seems to my unschooled eyes as though a lot of pretty big bugs make it into releases. Does inadequate QA cause bugs to go unnoticed until users find them, or are releases done in spite of major bugs?
Hi Brycef46143366, I understand your frustration here. The XD team does its best to ensure that an update has no major bugs that affects user experience with the product. All bugs reported thereafter are prioritized and addressed as soon as possible. Can you list down the issues that you are facing with XD so that we can better address your question?
Hi Atul. You need only search the forums for my posts by name. Why would you ask me to list all of the problems again, here? That's entirely too common an approach for the XD team - asking the user to do the QA, asking the user to describe the problem over and over again. Honestly, your best is not nearly good enough.
You'd assume an application like this should at least have its act together. But the truth is that no developer can fully anticipate all the different configurations and actions users will use and apply in a real world situation. And then there are also a lot of issues outside of the team's reach – like trouble with being properly signed in (authentication) and having a correctly installed application (app deployment and management).
As errors and bugs surface, they're being put on a list for a solution. But this kind of work is like a scheduled train service. It runs on regular intervals, and any late-coming or surplus passengers will have to wait for the next train. (Adobe is probably using some Agile Sprint workflow.) Most of the non-lethal bugs are simply collected and handled that way. It's business as usual fo the developers...