Kindle Fire HD – TechCommGeekMom

When I first read the title of John Daigle’s Adobe Day presentation, “Enjoying a Smooth Ride on the Mobile Documentation Highway,” guitar riffs by Steppenwolf echoed in my mind thinking of the song, “Born to Be Wild” and scenes of Peter Fonda and Dennis Hopper riding down the information highway. OK, maybe not the information highway, but with mobile, it’s an open road right now that is waiting to be explored.

While I hadn’t heard John speak before, I was familiar with his “rock star” status due to social media–mostly through Twitter (you can find him as @hypertexas)–in my e-learning and m-learning forums. It turns out that John is a big RoboHelp and Captivate expert, so being tied into the mobile highway scene makes sense!

The premise of John’s talk was that there are shifts and trends in mobile, and we need to look at organizations as early adopters, figure out the mobile landscape, and look at how user assistance is used on mobile as compared to how reference documentation is used generally. He pointed out that writing and designing for a mobile audience is very different from traditional methods (I agree!), and that he would be offering some hints on how to approach technical communications for mobile.

John pointed out that fellow speaker, panelist Joe Welinske, created the “bible” for Windows Help, and now has created the “bible” for mobile apps, referring to Joe’s book, Developing User Assistance for Mobile Apps, which talks about the “screen wars” between the smartphones and tablets of various size. These various sizes produce a challenge for technical communicators. John went on to point out that e-readers, such as Kindle and Nook, are still alive and well and doing well as compared to other tablets such as iPads and Samsung Galaxy Tabs. The initial conversion of print text to Kindle ePubs was a big change in electronic documentation. He also stated that at this stage of the game, Windows Surface and Windows Phone are a little late in the game, but they are catching up rapidly.

Following some of the comments of keynote speaker, Charles Corfield (the post on that talk is forthcoming!), John explained that other products including voice-activated devices, such as those found in some cars these days, are becoming more prolific. Google Glass, which is getting a lot of press right now, is a new game changer in mobile devices, and time will tell what kind of impact it will have.

John told us that as of February 2013, there were one billion smartphones and 150 million tablets worldwide–proof that mobile is becoming more widespread! Corporations are even getting more involved in mobile by buying mobile devices for employees, but many companies are also allowing BYOD (Bring Your Own Device). Companies are starting to embrace the idea of BYOD a little more lately.

Finance and healthcare industries are quickly adopting mobile delivery of information because of the portability of the devices. Mobile devices are being used more in industry and shop floors because they allow users access anytime, anywhere. John informed us that many of the same technical communications skills and experiences needed to write standard information apply to mobile. QR codes are gaining popularity as a part of the movement of accessing documentation through mobile. John quoted Jakob Nielsen saying, “Killing time is the killer app of mobile.” With that in mind, John advised that technical communicators should learn to use more economic words for mobile, such as “extra” instead of “additional.”

John also quoted John Caroll, who said, “Minimize the extent to which the systems and the information get in the way of what the user’s really interested in.” Progressive disclosure is key in writing for mobile. It allows one to gain information by revealing what’s needed when it’s needed. Ways to show this in mobile interfaces could be drop-down navigation or overlays. This allows a user to not leave the page, but he or she can still get to information quickly. In this sense, mobile can go right to the source or the heart of information needed.

So the question is, are huge documents (such as what’s in those big company binders) going mobile too? The answer is that technical writers can’t just dump desktop layouts and information onto mobile. This is where technical communicators need to work with developers to do what they do best–help “champion the end users.”

Going mobile is about flattening navigation–but not going button crazy, and getting back to context sensitive help. Technical communicators need to tap into social media to keep content current and accurate, thus becoming curators of user generated content.

It helps to prototype mobile layouts with rapid wire-framing tools, like Balsamic Mock-ups as a popular example. There are many specific tools on the market that are available to assist the developer in facilitate context-sensitive help.

However, there are several design controversies involving the need to upgrade browsers, progressive enhancement, adaptive design and responsive design. Some argue that responsive design is not the best because it makes a device’s CPU works harder, thus it becomes a virtual memory hog when resizing images as needed. Yet, responsive web design can adapt layouts to the appropriate viewing environment with fluid, proportion-based grids.

John suggested using the site, http://HTML5test.com , to help test how compatible your site is with mobile interfaces. He also pointed out that help-authoring tools can do much of the work with single source layout concepts, as different settings in authoring tools can help determine how to make user outputs work properly. Another such tool he recommended was Adobe Edge, as it helps writers to preview and inspect web designs on mobile devices directly ON the devices. For additional tools and information, John pointed us to his website, http://www.showmethedemo.com .

I particularly enjoyed John’s talk, as I’ve been following many of his posts on Twitter for more than a year now. He’s very good at explaining the power of mobile in technical communication, and I think John put this perspective well into view for the Adobe Day attendees. As many know, I’m a big believer in the power of mobile, and the mind-set for writing for mobile isn’t that difficult if you understand the basics. So, it’s good that Adobe continues to include information about technical communications in the mobile world, as that’s where a lot of change is coming in the future. Adobe made a good choice when asking John Daigle to present information about mobile documentation.

John, if you are reading this, please feel free to add any comments or corrections in the comments! 🙂

Just within the last month or so, I’ve been made aware of two tablet computers made for especially kids–and ones that weren’t something like a glorified LeapFrog or VTech toy. There is a place for LeapFrog and VTech-type tablets for the preschool/early elementary school set, but the ones I list below were recent ones that I became aware of targeting the grammar school demographic.

The first one I saw was the Tabeo tablet. I read about it in the following CNET article:

Toys ‘R’ Us unwraps $150 Tabeo tablet for Kids

The Tabeo, according to the article, is an Android-based tablet that includes drop-safe bumpers, wi-fi, and parental controls, and will only be available through this toy selling-enterprise.

The other kids’ tablet that I came across (and I don’t remember how–perhaps watching TV with TechCommGeekSon?) is called the Meep Tablet, which is being released by Oregon Scientific.

You can find the product website here:

Meep Tablet

It, too, is a tablet that runs on an Android OS, has drop-safe bumpers, wi-fi, and parental controls, and it appears that it is sold only through Oregon Scientific.

What would be appealing about these tablets, which are targeted for the ages 6 and up crowd? Part of the appeal would be the price– about $150 for either tablet. Yes, the parental controls and such are nice features–no denying that, but what else? Neither item has much memory, and if kids are going to use these tablets for games, then they need a lot more memory than what a first generation iPhone had. While memory cards can be added, why go to those lengths? Why not just put decent memory chips in the devices in the first place?

Being that I’m an m-learning TechCommGeekMom, I also tried to think about how such devices would be good at a school setting. Could they be used in a school setting? I suppose they could be on some level, and it’d be a decent investment for a school at just $150 a pop. Schools could control the content, using the parental controls. The bumpers used to protect the devices would allow for some longevity for the devices as well. The devices still have video and web cameras, and are still wi-fi enabled. Since they run on a version of Android, they could download Android apps.

But is buying either of these devices worthwhile? Since only the Meep in available now, and the Tabeo is coming out in a few weeks, we’ll have to see what the big reviews say. I wouldn’t mind reviewing them myself if I could get a hold of each of these, so in the meantime, I can only go by what each manufacturer has promoted.

But in thinking about the age group of “6 and up”, and thinking about my own son and how I would want to invest money in a tablet for him (if he wasn’t usually borrowing my iPad), why would I bother to get a kiddie version that’s barely expandable or that could be updated with later software, and had more memory?

My first thoughts turn to the idea of the rumored iPad mini. Oh, if that was out there (and I had the cash), I’d buy that in an instant for my son. Why? Well, first of all, it’s no secret that I LOVE my iPad. I love the variety of apps available–both educational and for games for him. Since he has to use my iTunes account to download apps (and I don’t give him my password), I can supervise what goes on the device and what doesn’t. That seems like parental control to me. I would be able to use the “Find iPhone” app to track him as well, as needed. It also would much more internal memory, I should think, than what the Meep or Tabeo is offering. Even if it only had a 8GB or 16 GB memory, that’s better than the base memory offering of Meep or Tabeo. Additionally, there are already school programs out there using iPads, so adapting to iPad minis would be an easy transition for many schools, and be easy for kids to use due to its smaller size for smaller hands.

This leads my thought stream into thinking about Nexus 7 tablets, Nook HD tablets, Samsung Galaxy or Kindle Fire HD tablets. Why not get those for a child? They are smaller Android-based tablets as well, right? Well, the prices tags are a little higher, that’s for sure. In most situations, however, several of these tablets are not THAT much more money, and yet there would be more flexibility in these devices. I was just even reading a rumor that Microsoft’s Surface tablet may come in a variety that’s in the $200 range. Talk about flexibility compared to some other tablets, even if it’s still more of a PC than a tablet! Why wouldn’t a parent invest in that type of tablet instead, knowing that there are more apps, more downloadable programs, and more memory with these machines?

Business Insider recently posted this article comparing tablets, and it’s worth a read:

The Only 7 Tablets Worth Buying Right Now

Of course, my money is on the hopefully impending iPad mini. But even if that never comes to fruition, these other tablets provide some good bang for your bucks. I think cheap childproofing bumpers and kid-friendly can be found on eBay and other retailers, if that’s a concern. But I see these other mainstream tablets being a better investment, as they can grow and upgrade with your child better than one “made for children”.

My child is part of the demographic that the child tablets are targeting. He’s now 11, and is a very different child than when he was 7, 8 or 9 years old. His tastes and needs have changed in just a few short years. Heck, he’s even upgraded his Nintendo DS two times in the last three years, because he wanted better memory and flexibility with the DS apps offered, as well as more powerful hardware. He might not put it in those terms, but even he knows the game. (No pun intended there!) Looking at tablets for growing kids should be looked at the same way–a tablet, for the investment, should be able to grow with the child, and a regular tablet would better suit those needs. With a regular tablet, not only would there be personal flexibility with games and apps, but more opportunities to use it for educational purposes–for homework, classwork, etc.

And that’s TechCommGeekMom’s take on that. If some manufacturer wants to send me one to be put through the TechCommGeekSon wringer, or if someone has had a different experience with a made-for-kids tablet, let me know. I’d be glad to share your experiences in a post here.