For some users, the software provided for the stationary eye trackers don’t meet their needs. To allow them to do what they need, an SDK is provided with which software can be developed to communicate with, control and get data from the suppliers stationary eye trackers. The SDK was being rewritten and the documentation which previously had only been available in PDFs should be made available on a web site instead. In this project, I was given the role as the tech writer, information architect for the documentation site, and designer of a software provided to help users set up their eye tracker correctly.
Examples of actions in the project as the…
…Tech writer
Explain common concepts
Purpose: To provide knowledge in an easy to understand way for developers who want to write eye tracking applications
Method: Using text as well as images to explain concepts in a way that should be understandable by the target audience.
Outcome:
There is a section on the SDK website where the user can read about the concepts, but also find more information if needed by going to linked resources. The section contains both text and images.
…Application designer
Iterate designs
Purpose: Try out different design options to see what works and what doesn’t
Method: Generate several options for the same screen and iterate together with a graphical designer
Outcome:
By making wireframes of different concepts with the actual copy that should be used in the real application and making clickable prototypes it was possible to eliminate those that wouldn’t work and continue iterating the ones that had potential.
A skilled graphical designer who also worked with other software in the company turned the wireframes into more polished design that also kept in line with the look and feel of the other software developed in the same business unit. By working together we quickly arrived at something good enough to be used in usability testing to further collect input for iteration.