With all the news about the skyrocketing demand for smartphones overtaking computer purchases, you might think that technical writers would increasingly need to focus on writing and delivering user assistance for mobile devices.
For technical writers, writing for mobile appears to be the next big thing. Here are a few examples:
- Mobile devices will be the primary connection tool to the Internet for most people by 2020, according to the Pew Research service.
- References to mobile phones and tablets are abundant at the WritersUA conference and the upcoming Society for Technical Communication conference.
- Help authoring tools such as MadCap Flare and RoboHelp tout that they support publishing content for mobile devices using the ePub output.
- There’s even a book dedicated to the topic called Developing User Assistance For Mobile Apps by Joe Welinske.
So along with social media, one might think that creating user assistance for mobile devices will revolutionize the way we work. There’s one problem though. In the last year, I have yet to see one job description in Vancouver that explicitly refers to preparing content for mobile devices. When it comes to technical writing opportunities, Vancouver is no Silicon Valley but it’s not unusual to see five to 10 advertised jobs per month.
I don’t think anyone can argue that creating user assistance for mobile development is too new. According to Apple’s web site, there are reportedly 500,000 applications for the iPhone and iPad. There are also thousands of applications that run on the Android operating system. And smartphones have been available for years. So why is there not a surge in demand for user assistance for mobile devices? Some guesses:
- Software developers are writing the content. While the user assistance written by developers may not be professionally written and formatted, perhaps management feels that the content is “good enough”? After all, if a mobile app requires a lot of documentation, it probably means that it’s difficult to use. Users expect apps to be simple.
- Perhaps writing for mobile is not big as predicted. Employers in Vancouver are not clamoring for writers with mobile experience. To be fair, I searched for “technical writer mobile” on the U.S. job site www.dice.com and found that 41 of 649 jobs mentioned “mobile” in the job descriptions. Hardly a tsunami!
Mark Baker says
Considering that technical writing in general has not really adapted to the web, which has been mainstream for a decade, I am not expecting any rapid shift to mobile any time soon. Actually, if tech pubs actually did move to the web, that would acomplish 80 to 90 percent of what is needed to move to mobile.
I really can’t see any great need for help for most mobile apps, which tend to be pretty simple and straightforward. Navigating help on a phone might be more challenging that just figuring out the app for yourself.
The possible use of phones and/or tablets for viewing docs for other product is more interesting, though, especially if combined with the use of the mobile device as a diagnostic tool. Unless the user is going to be off the net, though, web-ready docs should also be mobile-ready, as long as the writers do not get carried away with complex layout and tables.
What I fear is that people who are still having a hard time letting go of long-form docs may see epub as the successor to PDF and use it as an excuse to continue to avoid creating real topic-based content.
Robert Desprez says
Thanks for your comment Mark!
In my mind, mobile devices have revolutionized the lives of millions of people but it seems that our jobs may in fact change very little, at least for the short term. It reminds me of the development of social media, which most people would agree has radically altered how we connect with each other and communicate. Given that we are in the business of communication, I find it surprising that it doesn’t appear to have changed technical writers’ jobs that much.
John Mulvihill says
Oh, UA for mobile is coming, all right. The nail-biting question is, are we ready to adapt to the forms it will take?
Will tablet-scale enterprise apps cling to the gothic help systems and reference manuals that documented their ancestors on the PC? With companies’ investments in content management and all those legacy docs, it would be easy to give in to temptation and publish mini-me docs for the tablet, at least in the enterprise world.
We need to keep in mind that today’s mobile is about where the PC’s processing power was around 1982, when compared with the platform it was about to replace, the mini. Mini-originated word processing apps like Wang’s persisted for years on the PC until finally knocked off by Word.
Small developers, like the tens of thousands writing for iOS, place docs at about the same priority level as taking the recycling out of the lunch room. They’re engineers, after all, so everything is about the product, not the user. Down here in Silicon Valley I’m John the Baptist, evangelizing to developers of sophisticated iOS apps that UA needs online representation in their mobile products.
The dearth of authoring tools for mobile UA (ePub does not count) has given me license to pitch socials-based help to the iOS developers. This month I’m cleaning up the UI for a Beijing developer of a clock-radio product in the App Store. Following next month’s release of the new build, I’m going to lay the groundwork for socials-based UA, where users will be able to interact with other users, and with the developer. In fact, because this is a fun app, users will be able to compete to provide future content, like alarm sounds.
My sense is the socials will influence UA as much as the platform shift to mobile. The generation who grew up with the socials want their relationship with the developer to be an equal one, where the user can suggest new features or more efficient procedures. Perhaps the disruption to UA caused by social/mobile will enable us to break free from the print paradigm that dates back to when users were chained to workstations.
Imagine mobile devices a few years from now not requiring keyboards for input. Imagine every voice call being a video call. Imagine cubicles without workstations. Imagine Siri running on a quad-core processor and being five times smarter. Docs will still be required, but their form, content, and delivery will be completely different. Will we be ready? We should be planning and preparing for big changes, or our tenure could be undermined by the UX crowd.
I think some documetation authoring developers have their heads in the sand. Things are going their way so why disrupt the status quo? I hope I’m wrong about this.
It’s natural for veteran writers to decry the end of the printed word as the currency of our trade. But think of the possibilities. No more printed manuals, or management of multiple versions of same. There will be content management, only this time it will be interfaced with an AI-based delivery system. How exciting is that going to be? Users will engage in dialog with the knowledge avatar and we’ll have a hand in the script. As the social model of collaboration is instilled in enterprise software, we will benefit from direct communication with the end user, and the user will have access to their peers.
We are entering the most dramatic metamorphosis in information technology ever — bigger even than the introduction of the PC. If we stand up for the right of users to be informed, and if we pioneer AI-based, socially-oriented knowledge resources that won’t even be perceived as docs, we tech writers stand on the threshold of making documentation relevant again. Even on mobile devices.
— John Mulvihill, BA (CMNS), Simon Fraser University, Class of ’92
Joan Francuz says
I feel like an old curmudgeon watching a rerun of the same thing when [pick your era] personal computers arrived on people’s desks, desktop publishing arrived, email arrived — no one ever thinks they need documentation or training until they’re past the point of no return. Current rant precipitated by trying to use a new Mahjong app on my iPhone. Of course I checked the help. Hah.
Robert Desprez says
Hi John,
Thanks for your impassioned response! Sounds like you are immersed in some very interesting projects.
I hope you are right: I would like to see more focus placed on user documentation for mobile. It could be more work, more variety, and some exciting challenges for technical writers.
K.Vee.Shanker. says
Hi Robert,
As John Mulvihill says, technical information might take a new avatar. If you think simple field-level help, yes, no one is interested. When you want the users to go beyond the ‘normal’ use however, help files will be demanded. No one will refer to help for formating a simple letter. But, if you want to make a user guide, technical help is inevitable. It is similar to the content management skill that has taken off. No one would have foreseen it some years back.
I foresee technical writers with mobile experience in demand within a year or two. Until then, take it as one of the sectors to watch!
sudhir subudhi says
Hello Robert,
There is no question that people will go mobile. Computing will go mobile to compensate the need for people to perform tasks on the move.
As you have pointed out “Software developers are writing the content” is seemingly the big reason why companies don’t hire technical writers for the job. Current smartphone apps are very small and are simple to use. So they need very little in the way of instructions. The apps can be designed in such a way that they can do away with this little amount of documentation.
I have downloaded many Android apps and have run them successfully by reading only one page Release information that can be read before downloading the app.
Bruce Conway says
Seems to me the whole point of mobile is to steer the user towards “dumb and simple” (excuse the terminology). I’ve talked to mobile users who assured me that they were “computer illiterate”, almost as if mobile has nothing to do with computers, or at least is a different universe altogether.
User documentation for mobile, then, might be seen as admittance that mobile is not easy, that it needs explaining, so we have to have little popups or animated characters that say “Press the Volume Up button!”, and so on. But these features pride themselves as “given“s in the mobile world — not in need of explanation, user-friendly, user-obvious, intuitive. So, why go printing pages of instructions for the smartphone enduser? Rather than a tech writer, you’d need something more along the lines of a user interface expert, rather than a tech writer per se.
Bruce Conway says
Another aspect is the communication model used in traditional technical writing versus mobile. Mobile would be classified as “two-way, symmetric” (information is exchanged freely back and forth between two parties or audiences) in Grunig’s 4‑Models of Communication whereas help-systems and manuals are usually “one-way, asymmetric” (they push information outwards to an audience).
If you need help on your computer, a realtime chat session (2‑way, symmetric, where the help author talks “with” you) is actually several levels more useful than having to read 7 pages of how-tos and checklists — where the help author is silent and distant, merely pushing the information at you in a generic and unfriendly way via paper or screen (“one-way, asymmetric in Grunig’s models).
Wireless and instant, being “right there” in the moment seems to be the new wave, and is likely affecting the way we communicate. The language, for instance, is already acronym-ridden, shortened, briefer, more efficient in some cases, lean and mean to save bytes and travel quickly through wires and probably bounce off multiple satellites.
Social media in general is in fact changing corporate communication models to more “two way, symmetric”. Companies can now respond to complaints more quickly and effectively using Twitter, email, websites, chat sessions and so on. They’re not messaging so much as they’re now conversing, and the new buzzword “listening”. Two-way, symmetric “conversations” stress listening on the, usually, corporate side of things rather than pushing questionable or annoying marketing instruments out at an unsuspecting but still suspicious public.
Grunig revisited: digital communication and the Four Models of Public Relations
Posted on September 14, 2012 by Stephen Waddington
http://wadds.co.uk/2012/09/14/grunig-revisited-digital-communication-and-the-excellence-model/
In other words, they’re listening and starting to chat with us more in a vibrant and realtime kind of way, rather than relying too much on static unfriendly Help systems and manuals, thus putting thousands of unsuspecting technical writers out of work. (joke, I hope).
This kind of thing is studied in “Communications Management” (called Public Relations). It might also fall into the sub-area of Rhetoric or Sociology, but Grunig seems to be the guru behind all this research, starting in only 1989 ? or so. For instance, it turns out that companies who do switch to a more two-way, chatty, friendlier, open, equal, listening, helpful style of communication with customers actually improve their business, are generally classified as “excellent organizations” (in the public relations framework developed by Grunig) and make more money!
In any case, smartphones and iPads seem to inspire a i) realtime ii) briefer iii) on-the-spot problem-solving iv) two-way, friendlier kind of communication that may or may not replace traditionally-prepared technical writing instruments, such as Help Systems and manuals.