Help file production is very fast and high quality. Well-chosen default settings mean that I can get a technical document produced quickly, yet it permits deep access for customizations of document appearance, styles, etc.
One of the exciting aspects of Dr.Explain for me is that it is NOT AT ALL limited to creating Help files, but rather it is generalized toward the tasks that are a part of thoroughly and accurately conveying just about any technical ideas. The team that created this software focused on ease of use in this aspect: taking graphic images and adding call-outs to them, and making it very easy and fast to explain each call out. Any technical document requiring pictures, diagrams, and detailed explanation of parts of any graphic image [especially screen shots]) is made super-easy to create. When all the ideas are in place and in final form, just press a button to export the whole document to your desired format (including uploading to your web server).
Imagine you are asked to create a User Guide for a new product, that takes some understanding to use correctly. Anything from a fancy blender to an automobile, and even extensive mechanic service manuals. In my opinion, Dr.Explain is the perfect tool for such things.
Now, last, but far from the least, the most streamlined aspect about creating documentation with Dr.Explain is the task of documenting SOFTWARE! This is one of many places that Dr.Explain excels: it has nicely integrated features that let you grab screenshots of software, while automatically (and intelligently) adding the needed call-outs. It works SO WELL because it actually directly examines the user interface components of the running software itself. This advantage permits Dr.Explain to do 90% of the work for you.
At this point, I'm a very happy Dr.Explain user, and I'm not even looking or thinking that I will ever need any other technical documentation tool.
As a programmer myself, I would really love to be able to directly interact with the XML file that Dr.Explain packages its projects in. However, note carefully, that this NOT because of any shortcomings of Dr.Explain, but because I would like to, for instance, build a tool that helps in the task of producing a thorough professional-quality index for large documents. The tools for creating an index in Dr.Explain are GREAT -- which is why I would even consider spending time automating part of the process. In producing ANY high-quality index, however, there is a great deal of thought and human intelligence required. This will always be the case, regardless of automation. However, being an expert index-creator myself, I can envision add-on products that might assist with the process (e.g. plug-ins, or perhaps an API if they don't already have one) that permits external (or add-on) software tools to work with Dr.Explain document contents. I realize I'm pushing the Dr.Explain vision possibly farther than they have made plans for (yet), but I secretly hope that we might work together on such things in the future. (See my article on How to Create an Index: http://crystal-clear-research.com/drexplain_experience/how_to_create_an_index.htm .)
I write firmware for a firm that produces high-end 3rd-party products for the motorcycle racing industry (and I suspect we will be expanding into the car racing industry in the not-too-distant future). Some of these products are very technical in nature, and require in-depth knowledge to use them correctly. Simultaneously, we want to provide our end users with all 3 of printed and/or printable, tree-structured HTML help files, as well as on-line versions of the same thorough documentation. Dr.Explain is perfect for our needs.