TheSwamp
Code Red => .NET => Topic started by: BlackBox on May 21, 2013, 09:34:51 AM
-
AutoCAD API Wishlist Survey 2013
It is my pleasure to announce the launch of the AutoCAD API wishlist survey for 2013. I hope you’ll be willing to give 5-10 minutes of your time to take the survey – the results will be used to guide the efforts of our engineering team.
Click here to take survey (https://www.surveymonkey.com/s/JWHQGTJ)
The survey will remain open until 21st of June 2013.
DevBlog article here (http://adndevblog.typepad.com/autocad/2013/05/autocad-api-wishlist-survey-2013.html).
-
Do they have a survey on their survey? How about - "start at the beginning and not at the end". We all know what "Submit" means, right? (see pic of the first screen of the survey) Apparently not. Sheesh.
My first impression of the survey from that first screen was "huh? No questions? I must have missed it." My second impression is that they really didn't ask many questions, apart from asking me to identify myself twice.
Yeah, I'm being nitpicky but it's a good example of how Autodesk just don't relate to the user-experience expectations, or the priorities, that the rest of us take for granted. The AutoCAD user interface's departures from Microsoft's user interface guidelines (http://msdn.microsoft.com/en-us/library/windows/desktop/aa511440.aspx) and their API's ever-changing ways are other great examples of this.
-
And the one for the Civil 3D API:
DevBlog Article (http://adndevblog.typepad.com/infrastructure/2013/05/autocad-civil-3d-api-wishlist-survey-2013.html)
Please, everyone place their marks for Parcels and Grading, do what you want with the other one. :-)
-
Is there a difference between a "Survey" and Marketing Research?
-
Do they have a survey on their survey? How about - "start at the beginning and not at the end". We all know what "Submit" means, right? (see pic of the first screen of the survey) Apparently not. Sheesh.
My first impression of the survey from that first screen was "huh? No questions? I must have missed it." My second impression is that they really didn't ask many questions, apart from asking me to identify myself twice.
Yeah, I'm being nitpicky but it's a good example of how Autodesk just don't relate to the user-experience expectations, or the priorities, that the rest of us take for granted. The AutoCAD user interface's departures from Microsoft's user interface guidelines (http://msdn.microsoft.com/en-us/library/windows/desktop/aa511440.aspx) and their API's ever-changing ways are other great examples of this.
Their surveys are more-or-less kabuki dances.
Their marketing objectives define what they do, and the customer's opinion doesn't really come into play. For API related issues, it never has. Their API development has always been driven by their own internal functional requirements and little more than that.
-
Do they have a survey on their survey? How about - "start at the beginning and not at the end". We all know what "Submit" means, right? (see pic of the first screen of the survey) Apparently not. Sheesh.
My first impression of the survey from that first screen was "huh? No questions? I must have missed it." My second impression is that they really didn't ask many questions, apart from asking me to identify myself twice.
Yeah, I'm being nitpicky but it's a good example of how Autodesk just don't relate to the user-experience expectations, or the priorities, that the rest of us take for granted. The AutoCAD user interface's departures from Microsoft's user interface guidelines (http://msdn.microsoft.com/en-us/library/windows/desktop/aa511440.aspx) and their API's ever-changing ways are other great examples of this.
Their surveys are more-or-less kabuki dances.
Their marketing objectives define what they do, and the customer's opinion doesn't really come into play. For API related issues, it never has. Their API development has always been driven by their own internal functional requirements and little more than that.
I agree 100% with that summation.
We only need to look back over the published results for last several years to deduce that the API user is largely ignored.