Most of my readers and followers don’t use it. However, Flash finally gone does affect us. InDesign quit using Flash quite a while ago using HTML5 instead. However, I thought I’d mention this for those it might touch. In an article today in Direct marketing News, it explains the final nails in the coffin of Flash.

Flash finally gone doesn’t affect books—Yay!

This is why I suspect most of my readers and followers don’t use it. Adobe InDesign took this path several years ago—starting with the release of InDesign CC in January, 2014. In fact, this is why CC is necessary for book publishers. Well done ePUBs were not possible with InDesign CS6—you still had to mess with the code to get it done.

Since the release if CC, and especially CC2014, InDesign exports excellent ePUBs which need no clean up. Here’s one example from Book Publishing With InDesign CC:

“The big news, for me, with InDesign CC is that they can now embed fonts: These ePUBs are accepted by everyone except for e-ink ereaders. You have to encrypt the fonts to embed them. But the finished ePUBs upload fine through iTunes Connect, Kobo Writing Life, and Draft2Digital. Eventually, this will be commonplace and InDesign is leading the way.

Even though the ePUB spec says we can embed fonts, this is still spotty—not because it is difficult, but the ereader and reader support is usually missing. Most readers have gotten so used to the ugliness of standard fonts and limited typography that they change your books to fit their expectations. That will radically mess up your typography. My current recommendation is still to embed fonts for iBooks, Nook, Kobo, Scribd, and so on. For the Fire and Fire HD, we can embed Fonts. But you must make sure that you are using fonts with the proper licensing. You can also read embedded font ePUBs in BlueFire and Readium.”

But it goes much further—and many more big changes are coming for ePUBs. Some of these changes are the result of no longer needing to worry about Flash, at all.