Skip to main content

Productivity Tools and Religious Wars

I used to be a Tech Writer not that long ago and still have many professional and personnel friends who travel in those circles. So, when news hit the web today of the impending demise of Macromedia RoboHelp, it in my inbox pretty quickly. To scale the news up a little bit for relational purposes, imagine the ripple that would emanate throughout web design sphere if Microsoft moonlighted FrontPage. (Oh, what sweet dreams I dream.) FrontPage isn't the de facto tool for web design, but it's pretty popular and has a loyal following.


That's RoboHelp; it's got its quirks (read: huge-ass bugs that will totally screw up your week), but it's got its good points, too. It has also ceased to be very innovative in the past few years. Just before eHelp was acquired by Macromedia, they introduced FlashHelp, which was basically a Flash UI on top of standard web-based Help. Most of the new product innovations and solutions were aimed squarely at...well, that was the problem. They had answers in search of a question, and were starting that "enterprise systems" mantra/death roll.


There are better products that RoboHelp, certainly, but the entry-level tech writer could be relatively effective with it within a week or two, and be pretty proficient after a month. Not a bad ramp-up time considering that some competitors required a base-level understanding of object-oriented single-sourcing to kick out a Help system. (Note to AuthorIT; you have a kick-ass product but you need to lower the entry threshold. Writers != database admins.)


RoboHelp's departure from the market, while surprising, is almost exciting. The void that will be left behind is sizable. I don't have real numbers, but if I had to guess, I wouldn't be surprised if RoboHelp had over 50% of the market share. Now, sunsetting doesn't immediately invalidate all those licenses out there, but it does make support tougher. Many writing companies will move away from RoboHelp. Where they move is the big question.


The major players left standing are FrameMaker with Web Works Publisher, AuthorIT, Doc-To-Help, and Web Works for Word. Honestly, they all have pros and cons, as most tools do. Web Works has the best position because of the number of companies using or going to FrameMaker for single-sourcing. AuthorIT, while great on paper, is a complete philosophical change in process for tech writing houses, and I bet that breaks a lot of deals for them. Web Works for Word is young and, well, works inside of Word. Word doesn't exactly endear itself to many writers.


What will happen? My prediction is that another,single tool will rise and fill the void, instead of the other products gaining marginal market shares. The tool that rises will be one that will support the new scheme of Help development inside of Longhorn Aero and be able to do some cool build tricks with XML (they'll call it single-sourcing, but it will be glorified source-control). Frankly, I think the old RoboHelp team, headed by Mike Hamilton, now at MadCap Software, will get to make the product they should have made before.


And, a note to Mike and his team. You were really, really close with RoboHelp. Honestly. The code generation was a big sticking point; it wasn't critical, but just stop messing with the code. Give writers real tools to do real design: CSS, native XHTML, good layer controls.And clean up that UI; it sucks, and has for years. But, the conditional formatting, the multiple output formats, hell, I even liked the idea of Flash Help. Integrate with existing data management software (I still role my eyes a RoboSource Control) and let companies leverage investments they've already made.


Let writers fiddle and not get punished. Give them round-trip processes. In short, make the tool do what its supposed to do: let writers write, designers design, and everyone publish.


Do that, and you'll be bigger than RoboHelp ever was. If you don't, someone else will.

Comments

Popular posts from this blog

Happy Retirement Pat Sweeny!

In a previous life, I was an active member of the West Michigan Shores Chapter of the STC. I met a lot of really cool people there and learned a lot about what it meant to be not just a technical writer, but more about how technical writers can break out of the mold and accomplish things.

One of the people who did that was Pat Sweeny. Pat is (or was, by this point) the President and owner of The Bishop Company, a contract do-it-all house; they document, streamline and illustrate your process, and they do it damn well. Pat was one of the first people in that chapter to "get it", which is to say, he and his company understand that technical writing isn't going to be a department for very much longer, it's going to be a business.

He had the foresight to actually make it a business, but he also had something else. Pat was forever trying to better those around him. He would come to meetings (which was a big step beyond most people) and teach you things. Or he would come to …

Google Inbox: A classic Google product

My work domain (an EDU) recently had Google Inbox enabled so I had a good chance to try it out. My personal email is relatively quiet and, I believe, doesn't provide a good Inbox experience. Work is more active and requires actual management, something I've tossed many a tool at over the years. As part of my work life, I supported the Google Apps for EDU installation here and took a pretty extensive presentation to campus about how to manage large amounts of email.

Inbox is a classic Google product: the distillation of a number of excellent ideas into a set of half-complete features built for a use case most people don't meet. We've seen this in the past in products like ChromeVox, Google's Chrome extension for accessibility. ChromeVox works great on ChromeOS devices, but completely ignores the point that most users of accessibility tech (AT) don't have or want ChromeOS devices and come to services with their AT in tow. ChromeVox also ignores decades of convent…

Evernote

Evernote, for better or worse, is the best note-taking service for my needs. It works across all my devices/computers/modes. It's fairly easy to get stuff into it. Hell, they even have 2-Factor authentication. The Windows app is a little clunky and my girlfriend and I have never been able to get shared notes to work properly (conflicted note! three times in the same grocery trip!), but what service is perfect? At least they have nice socks.

Everything, in fact, is pretty good as long as you don't screw up. And screw up I did. I'm not very regular about making backups, but I do make them every month or so. Once you figure out how to create a backup, that is.

There's a helpful Export Note option (which turns into Export Notes when you select multiple notes HINT). The export process is essentially opening All Notes, selecting every note, and then choosing Export Notes. Or something like that; Evernote never tells you, you're left to figure it out on your own. The file…