Archive for rambling

Will the iPad change the face of publishing?

// June 1st, 2010 // 1 Comment » // books, iPhone, rambling

There’s been a lot of hype about the launch of the iPad this week. Many are claiming that the iPad and its iBooks software will save the publishing industry. They’re saying that it will kill the Kindle, the Nook, and every other ebook reader with a nonsensical name.

I say: not gonna happen. And here’s why:

1. Lack of an ePaper display.

This is the deal-breaker for me. Reading on an LCD screen causes eye strain after awhile. Not a big deal if we’re just reading blogs or news sites for a few minutes at a time. But when reading a book, I might sit down for hours at a time to read. With an LCD display, that’s going to cause eye strain. That’s the single biggest reason I would not consider this at all for a viable ebook reader.

The other side effect of not having an epaper screen is that I have to charge the thing every day. With epaper, a charge can last for days or sometimes even weeks. That means if I’m going away for the weekend, I don’t have to carry along a charger with a Kindle or a Nook.

2. Lack of Selection.

The official Kindle store has more than 400,000 books available. Barnes & Noble’s Nook has access to over a million books, newspapers, and periodicals. And that doesn’t count the hundreds of thousands of books available on sites like Smashwords and Fictionwise. The iBooks store currently has titles available from five major publishers. Which probably amounts to a few thousand books (probably more with backlists, but I bet it’s still less than a hundred thousand titles). So if you only read mainstream ebooks, the iBookstore might have everything you’re looking for. But more likely, it won’t. And it’s unclear how well iBooks will play with DRM-free ebooks from other sites.

3. DRM.

If iTunes is any indication, iBooks will have heavy digital rights management. The mainstream publishing industry embraces DRM, but it’s pretty clear that tech-savvy consumers (which is what the iPad is most likely to appeal to) don’t appreciate DRM.

Other Shortcomings

The iBooks software isn’t the only shortcoming the iPad has. First of all, the internal memory is really lacking. Sure, the most expensive version has 64GB of storage, but the base model (the one that’s only $499) only has 16GB. To top that off, there’s no SD slot. Which means I can’t expand that 16GB of storage. I can tell you how long that will last me. About a month if this is something that I’m watching movies on, listening to music on, storing photos on, and reading books on. That’s unacceptable.

The lack of an SD slot also means I have to hook this thing up to a MacBook Pro if I want to transfer photos to it. Which makes that photo software they were showcasing a whole lot less impressive. It doesn’t even have a USB port. Or an HDMI port. That means I can’t hook it up to my TV to watch high definition movies. What’s the !@#$% point?

A Better Alternative

First of all, if you just want a dedicated ebook reader, buy a Kindle. Buy a Nook. Buy an Alex. Don’t buy an iPad. If you want a giant iPod Touch, then buy an iPad.

The good news is that there’s a better alternative only a few months away. A company called Pixel Qi has come out with a new transflective display. What this means is that the display does double-duty. Let’s say you want to watch a movie. Then you use the display as a standard LCD. But then let’s say you want to read a book. You simply switch it over to epaper mode! And if you’re trying to surf the web in bright sunlight, then you can switch it over to transflective mode, which has less saturated color, but is easier to read in direct light.

And there’s a company based in India, Notion Ink, that has created a tablet that uses this new display. It runs on the open source Android platform, which means there are plenty of apps available, and it’s easy enough to learn to code them yourself. The best part? It’ll have expandable storage and it’s expected to retail for only $325. This is what I’ll be waiting for.

Flash CS5 SWF embedding issues

// May 29th, 2010 // No Comments » // Flash, awesomeness, rambling, web development

I’ve been messing around with this Flash CS5 30 day trial at work and thus far it will be a fantastic upgrade when I eventually buy it. Not because of new features or the “Adobe interface” (which honestly is just Adobe tabs wrapping old Macromedia UI elements), but because Flash CS5 is a Universal Binary for Intel powered Macs. And…wow. What a difference. CS5 launches in barely a second, the publishing of SWFs is incredibly fast, and the application UI feels much more responsive.

Anyway, on to the point of my post. Flash CS5 changes the default way the app publishes content. In addition to the HTML / SWF it has always created, it now creates a separate Javascript file that the HTML file must use in order for the SWF to appear in a browser.

Embedding with Javascript has been something most seasoned Flash developers have been doing for years, but until now its been kept away from general Flash users. CS5 changes all that. Every Flash user, from beginner on up, will be required to upload this JS file, as well as copy plenty more player embed code if they want to embed movies in a separate HTML document (and then figure out how to change the embed src link to the requisite JS file).

Was there a way around this? Not really. Macromedia/Adobe were caught between a rock and a hard place with the whole Eolas/Internet Explorer lawsuit – which forced a change to how the most popular browser on the planet (grrrr) embeds rich media content – and prevented Flash movies all over the web from auto-playing, not to mention those heinous “Click here to activate” confirmation dialogs. Including a Javascript file resolves these issues, but it’ll undoubtedly make life more difficult for Flash beginners.

What you don’t know, won’t kill you.

// May 28th, 2010 // No Comments » // e-learning, rambling

One cause of the frequent failures is that the real reasons for undertaking e-learning projects are not defined, are not relayed, get lost, or become misinterpreted. Instead of guiding projects through to the end, the success-related goals of enabling new behaviors are cashed in for the pragmatic goals of simply putting in place something that appears to be a training program. Because executives are not sufficiently attuned to the criteria against which their e-learning solutions should be evaluated, the focus of development teams turns to what will be assessed: mastering the technology, overcoming production hurdles, and just getting something that looks good up and running—within budget and on schedule, of course. The budget and schedule become much more the focus than the original goals. Surely operational success is the primary reason most e-learning projects are undertaken. Success comes from more responsive customer service, increased  throughput, reduced accidents and errors, better engineered designs, and consistent sales. It comes from good decision making, careful listening, skillful performance. Remember: Success for organizations and individuals alike requires doing the right things at the right times.

For the project manager given the assignment, the real reason for implementing e-learning easily transforms from the instigating business need of getting people to do the right things at the right times to the pressing challenge of getting the training project done.

What does this say about the real reason the project is being done? You have to wonder: If people think it’s so unlikely that any training program is going to be effective, perhaps the learning outcomes aren’t the real reasons for offering them. Unspoken, covert, and perhaps subliminal rationales may include thoughts that some sort of formal training, regardless of its effectiveness, will be better than nothing. That is, the real reason for implementing the training program might actually be to have the appearance of providing training. Otherwise, employees would complain and even have cause to do so. By offering a training program—any training program—the burden shifts to the employee.

What do you all think?