Robohelp or Doc-to-Help?
My client has given me permission to use whatever tool I want to do the next batch of tech docs — and they’ll buy the software. No cost to me.
Which one should I choose?
Robohelp or Doc-to-Help
Doc-to-Help was the first help authoring tool (HAT) I used in my technical writing career. We’re talking quite a while back now. Since then Robohelp has overtaken it as the tool of choice for technical writers, especially as it’s now owned by Adobe and bundled with its Technical Communications software pack.
For Doc-to-Help
- I feel this product is under-estimated. Other technical writers (more knowledgeable than me about HATs) recommend it.
- Opportunity to broaden my skillsets (self-interest here and not to the client’s advantage!)
- Rapid response from Component 1 (product owners) when I contacted them. Very helpful. Only Techsmith (esp Betsy Weber) were more helpful.
Against Doc-to-Help
- Price is not cheap
- Will there be enough qualified Doc-to-Help experts to take over this project when I move on?
- Does it integrate with other technical writing apps and/or Microsoft Word?
- Worried about lack of community support, i.e. from other technical writers, if I need help.
For Robohelp
- Oceans of Doc-to-Help experts to take over this project
- Part of the Adobe Tech Communication suite. Maybe get discount.
- Arguably the industry standard
- Plenty of tutorials online if I get stuck
Against Robohelp
- Price
- Concern that there is no real advantage in getting the Tech Communication suite anyway as we (i.e. the client) won’t use it once I’ve left
- Found the user interface horrible to work with last time. Admittedly, this was four years ago but you know how these things stick.
Another alternative is Madcap Flare.
What do you think?
If you were in my shoes, what would you do?
