Announcing the Readium Foundation and the Readium EPUB 3 SDK Project

As you may already know, today marks the public announcement of the Readium Foundation and the Readium EPUB 3 SDK project. Bluefire has made a big investment in this initiative, supplying executive leadership, development resources, and funding. We want to share our thoughts on why the work we’re doing as part of the Readium Foundation is so important—both to the future of Bluefire and to the future of digital publishing.

EPUB 3 is the expression of a dream. It embodies the publishing industry’s hopes for rich, interactive books of all kinds that are widely distributed and easily read on a broad range of PCs and mobile devices. But EPUB 3 will remain a dream without a robust, consistent rendering experience that works across a multitude of vendor and device platforms. As Bluefire progressed in its independent development of our EPUB 3 renderer it became clear to us that the EPUB 3 spec is open to a considerable amount of interpretation—and that developing a great EPUB 3 rendering engine would require substantial ongoing investment. So we started talking to and meeting with other interested industry players. What evolved was a small working group and a new dream: a collaborative project focused on the development of a robust, open source EPUB 3 rendering engine that each of us, and others in the industry, could use as the foundation for commercial-grade reading systems. The dream is now on its way to becoming a reality.

Publishers need to know that the books they release look great and function as intended no matter which reading application is being used—a Bluefire-powered application or an app from a developer or retailer from anywhere around the world. It’s clear that critical mass matters in ebook technologies. The challenge for the incredibly diverse range of digital publishers and retailers is achieving critical mass. Working together is a great start. We don’t expect the Readium open source engine to be a silver bullet, and it is unrealistic to think that every ebook platform in the world will utilize this engine. However, we do believe that the use of a common, shared rendering engine across a wide spectrum of large and small companies will be an important step forward—similar to the manner in which Webkit has facilitated consistency in HTML5 rendering across browsers, even in those that don’t utilize Webkit.

Bluefire has worked along-side the other initial founders of the Readium Foundation to bring this initiative to life. We will be working even harder moving forward to bring it to fruition. We will also be integrating the Readium EPUB 3 SDK with the Adobe Reader Mobile SDK so that our publisher, retail and library customers can use Bluefire-powered apps to distribute EPUB 3 content that leverages the industry-standard Adobe Content Server rights management system.

We know that many of you are hungry for details about when we will be rolling out our next generation apps, features, and pricing. We will share this information as the development effort progresses in the months ahead. Today, we’re celebrating: our industry has come together in an unprecedented way to help realize a vision of the future that creates and sustains opportunity for all—especially for readers.

– Micah

Customer-Friendly ACS

This is a post for readers of this blog who are currently using (or are planning on using) Adobe Content Server for the distribution of eBooks. Below you’ll find a few “best practices” for you to consider based on our experiences working with ACS technologies over the last several years. These suggestions mostly apply to retailers, but often require the agreement and cooperation of rights-holders and distributors to make these practices a reality.

  1. Enable customers to re-download purchased items multiple times.  Do not restrict a purchase to a single download. Avid readers often have multiple devices and acquire new devices over time.
  2. Enable customers to transfer content between devices. The Adobe solution provides the option to restrict a downloaded file to a “single device,” but it is rarely advisable to do that. While buyers can often re-download files directly to another device, there are many different reasons why customers may need to transfer files (a tethered reading device is a good example), and it is important that customers can back up their purchased files to future-proof against unforeseen events.
  3. Craft distribution agreements as a long-term commitment whenever possible—at least for previously sold content even after sell rights expire. Consumers fully expect to be able to re-download purchased content well into the future so it is important that retailers do not find themselves in a position where they are unable to provide that service. This fact is true with or without the use of DRM.
  4. Offer your customers free branded reading applications for mobile devices and desktop machines and tightly integrate your content acquisition workflows into these apps. This greatly reduces customer friction and builds your brand identity and customer relationships.
  5. Utilize the Adobe Vendor ID service that enables your customers to authorize their ereading applications with their retail store account credentials rather than having to go get an Adobe ID account. This enables you to offer the “single sign-in” user experience that consumers expect.
  6. Make sure that your reading applications support multiple user account authorizations for your customers that share devices with their spouse or child, or have multiple accounts for several other valid reasons.
  7. Enable customers to re-download purchased titles to devices that are authorized with a different user account. An example of this is enabling a customer to re-download a file that was initially downloaded to a device authorized with their Adobe ID account—to a different device owned by the same customer—but that is authorized with their spouse’s account credentials.  While many modern apps enable users to add multiple account authorizations to a single device, many older apps and devices do not support that. It is reasonable to limit this to two or three accounts as that covers the vast majority of valid use cases while limiting the potential for abuse.
  8. Offer customers an alternate download link option that is not “tied” to your own reading apps that enable customers to more easily read purchased items on their favorite third-party reading app or device that leverage the Adobe platform.
  9. Offer good help and support content and services.  Don’t try to sweep it under the rug or ignore it just because it is not an easy topic.

– MIcah

On the Adobe eBook Platform – Part 7 of 10: DRM

Digital Rights Management (DRM) is a hot topic these days for folks in the ebook business. There are strong opinions on both sides—pro and con. You won’t find me at either end of the spectrum. Bluefire’s mission is to develop technology solutions for the distribution and use of digital content that help our retail and publishing partners compete and succeed. Fulfilling that mission often comes with the requirement of supporting DRM protection. I have neither the luxury nor the responsibility to make decisions about when, or if DRM is used. When it is required we make every effort to execute on it well.

Given that perspective, my goals for this post are to explore why and how DRM is used, look at some of the challenges it can present to publishers, retailers and their customers, and to discuss some potential solutions.

Rights holders are concerned about sharing

The main driver for rights holders such as authors, publishers, and others to require DRM is to reduce the risk of lost revenues due to casual sharing of ebook files. This directly relates to the inherent nature of digital files where I (as a consumer) can buy an eBook, keep a copy for myself to read while simultaneously sending additional copies of it to my friends and family—some of which may have otherwise bought a copy themselves. The popularity of social networks amplifies this dynamic. A single consumer sharing an ebook with a few friends and family is not a big problem, but many thousands doing so can be. This is a REALLY BIG CONCERN for many rights holders. You can take the tact that there are other more important concerns or countervailing benefits, but any productive conversation on this topic has to begin with recognizing and respecting how passionate many authors and publishers are on this topic.

That said, one of the things that many of us really value about books we enjoy is our ability to share them with people we care about. So, it is worth noting that services can be crafted, that employ DRM, while still offering readers the ability to share in a meaningful way. In fact, a couple of the large ebook retailers already offer such services to their customers—though I personally find them to be a little too restrictive. There are many different potential approaches to enabling sharing. A service could enable consumers to share books with friends with a “loan” term that expires, or to share with a limited number of people, etc. My point here is that there is nothing inherent in DRM technology that prevents retailers and publishers from enabling customers to share content in a reasonable way –this is a “business rule” issue rather than a technological limitation. It seems to me that even just making it easy for readers to effortlessly send a preview of any book they are reading to a friend or family member would be very welcome.

But what about piracy?

A topic that is often unfortunately conflated with sharing is “Piracy.” In my mind, that term most usefully refers to folks that sell or freely distribute a collection of ebooks to the general public without permission to do so and without compensating the rights holders. This could be a real problem for some publishers if left unchecked, but commercial DRM is not designed or intended to address that particular problem. It appears to me that the only effective means of reducing piracy are enforcement, smart pricing, synchronous global availability, and consumer convenience.

However, DRM can aid in the enforcement efforts as retailers that sell unprotected content can be quickly identified as pirate sites by rights holders that require DRM.

A lack of a crisp separation between the concepts of “Piracy” and “Sharing” in regards to downloadable content is counterproductive to meaningful conversations around the ultimate cost/benefit analysis of the use of DRM—and I see that happen too often.

Beyond copy protection

One aspect of DRM is the symbolic message it can convey. One might think of it as a short fence: I can easily jump over it, but if I do, I’ve got a pretty good idea that I’m now standing on someone’s property. The point being that DRM is not always about just what it actually does–or prevents, but also what it communicates.

DRM can also communicate and enforce license terms such as how much content can be printed or cut and pasted from an ebook and can even control the resolution at which content can be printed. This can be important to publishers of high value content, such as industry reports and hi-res photography or collections of artistic works. It can also be important in documents distributed within an organization to employees and partners.

In some countries, there are federal laws that require that rights holder’s that wish to enforce copyright claims on digitally published content must apply DRM when distributing the content.

DRM in the supply chain

There is another, often overlooked aspect of DRM which relates to control and tracking mechanisms in the distribution channel. Publishing houses often choose a small number of partners that are entrusted with housing many thousands of unencrypted ebook files. These partners then re-distribute content through a wide variety of retail and library channels. In most cases, these files are directly fulfilled to the end customer once purchased rather than flowing through the retailer’s infrastructure. The agreements between the publishers and these distributors often specify robust network security systems and policies with a right to audit these systems. Beyond the security aspects of such an arrangement, it also offers a streamlined, auditable and track-able supply chain. DRM is not absolutely required in order to put such control and reporting systems in place, but it is worth recognizing that it is currently a key component in much of today’s digital book infrastructure world-wide.

Retailers and lock-in

By far the most unfortunate ramification of the allowance of the use of closed, proprietary DRM technology by major retailers is the vendor lock-in effect.

How serious this problem is for rights holders and consumers is a bit of an open question in the industry, with varying opinions and little hard data. That said, I don’t think that anyone would argue that there are no downsides at all, especially given the unhealthy level of consolidation that is occurring in the retail space.

There are some market trends that are helping to reduce the negative impacts of lock-in such as the unprecedented growth of multi-purpose devices like smart phones and tablets, and even the desktop is becoming a more popular reading platform. On most of these devices, consumers have choices in reading apps, and many use more than one on a regular basis. The growth of dedicated reading devices is slowing and many industry analysts expect that to continue.

As I’ve talked about in prior posts, the Adobe ebook platform was designed specifically to avoid the problem of vendor lock-in. There’s wide variety of apps and reading devices available from popular retailers and hardware manufacturers that support this interoperable system–including Barnes & Noble, Sony, Kobo, Books-A-Million, Hastings, Indiebound, and many others both in the U.S. and abroad.

(As this post is rather long, I’m reserving my comments on customer-friendly practices when utilizing the Adobe Digital Publishing Solution for eBooks for a follow-up post.)

The popularity of Kindle devices which utilize a closed proprietary DRM system presents a real pain-point for vertically focused retailers who would like to be able to sell content to Kindle owners, but can not due to rights holder’s requirements on the use of DRM.

There are potential solutions to this issue that don’t require dropping DRM altogether:

  1. Retail systems could be crafted that utilize DRM when fulfilling purchased content directly to a reading system that is tightly integrated with the retailer’s ecommerce system, but also offer an additional “Send to my Kindle” option. In this approach, the file sent would need to be a DRM free file (but could be watermarked). It would need to be recognized that a customer could side-load that item off of their Kindle device and share the file with others, but many publishers might judge that action to have sufficient friction for the subset of the retailer’s customers that have a Kindle device as to be an acceptable risk.
  2. Another similar option would be to offer the option of direct downloads of watermarked files for those customers that wish to side-load content to a third-party device or app that utilizes a closed rights management system.
  3. Retailers that utilize a proprietary content protection method in their own reading apps can also offer an option to their customers to download a file protected with the interoperable Adobe DRM. In fact Kobo and Google both do exactly that today. Rights holders could encourage other retailers to take this approach, and possibly even require it in the cases where they have sufficient leverage.

All of the potential solutions above (and there are others on the way) require the participation and agreement of the rights holders and the supply chain operators. The same applies to any change to the current status quo.

DRM can introduce barriers to entry for ebook retailers

One of the impacts of the use of DRM is that it adds additional costs for ebook retailers as they implement their back-end systems and conduct transactions. While these costs are relatively small for larger retailers, it can be a real hurdle for independents and retailers operating in smaller regional markets abroad. These retailers are an extremely important part of the overall ecosystem for many reasons, not the least of which is as a counterpoint to over-consolidation. They can be a real driver of discovery and innovation in the market–not to mention a source of significant revenue growth in the aggregate. This is especially true in emerging ebook markets abroad that are at the early stages of ebook adoption.

As the primary drivers for the use of DRM is the interests of the rights holders, it seems to me that it would behoove rights holders to consider ways to facilitate the diversity of ebook retailers by lowering barriers to entry. There are many means by which this can be accomplished both in terms of financial arrangements, technical support and consulting, shared infrastructure, open API’s and many others.

Helping ebook retailers compete and succeed by lowering barriers to entry is our core mission at Bluefire and we are making solid progress: we currently serve 80 businesses in the digital publishing arena in over 30 countries. We are ourselves a small independent company and I would very much welcome collaboration with publishers and distributors that have common goals and business interests in supporting the success of a robust and diverse marketplace for ebooks worldwide.

– Micah

On the Adobe eBook Platform – Part 6 of 10: Why Should I Care?

First, Some Context…

We are in the early stages of a very rapid global transition from print to digital for long format text content. This revolution will dramatically alter how content is created, distributed, sold and read. The changes will make a powerful impact on nearly every corporation, institution, bookseller, publisher, library and individual reader worldwide.

This transition is being shaped and greatly accelerated by the growth of handheld devices and by the adoption of reflowable document file formats, such as ePUB, that make reading on these devices appealing and productive.

Opportunity in Abundance

The opportunities that this revolution presents are immense for education, entertainment and professional development. The costs of production and distribution are dropping dramatically. Geographical barriers are disappearing. New markets and audiences can be reached on a global scale—in homes, offices, on the road, or sitting by the pool. These changes are enabling new business models.

Organizations have the opportunity to gain valuable insights into how, when and where content is used and to engage audiences in two-way conversations in contexts that were simply not possible before.

Challenges Too

This shift presents mighty challenges as well. Reading software can be time-consuming and expensive to develop and it requires rare technical and industry specific expertise. Content creators and owners are concerned about the ease with which digital files can be copied and redistributed, and thus they often demand the use of rights management technologies—which adds another layer of cost and complexity.

And while these technology hurdles are pretty significant, navigating the supply chain is a far greater challenge. That’s because most organizations (especially trade booksellers) must exist in an ecosystem of suppliers and service providers that need to integrate and coordinate with each other to survive and thrive. They require common file formats, rights management systems, fulfillment systems, licensing agreements, metadata APIs, and so forth.

The Age of Goliaths

This situation has set the stage for a very few large corporations with deep pockets and market leverage to make major strides early in this transition. These corporations are capturing large portions of the consumer ebook market, and perhaps more dangerously, mindshare. Of course, we’ve all seen how the Internet leads to monopolistic tendencies, or at least is a fertile ground for building market dominance. You can probably think of many examples of this: eBay, Google, iTunes, Craig’s List, Amazon and the list goes on… And in the world of books, we have the additional wrinkle of operating system and device makers with ambitions to become the world’s largest booksellers.

This threat of market dominance presents significant risks for almost all other participants in the digital publishing space including authors, publishers, independent and regional booksellers, educators, libraries and especially consumers. It is particularly troubling that these private ecosystems close off the opportunities for ongoing direct two-way communication between content creators, owners and their audiences, and the insights that can otherwise be gained from direct audience engagement.

And as we all know, when markets are dominated by only a few players it has a chilling effect on innovation, competition and consumer choice. When we are talking about the written word—the embodiment of culture and knowledge—the stakes are high indeed. Let us not forget that the book business is larger than the global music and movie businesses combined.

David’s Slingshot

The Adobe eBook platform is not the only solution to these challenges, but it is an important tool that levels the playing field. Adobe provides essential pre-built technology components and services that would otherwise be prohibitively expensive and time-consuming for each organization to develop in-house. These technologies, along with a globally diverse range of distributors, aggregators, developers, libraries and digital service providers already participating in the platform, create a robust ecosystem that lowers the costs and other barriers to entry for new participants allowing them to quickly innovate, iterate and thrive.

The Adobe eBook platform is not just about DRM, albeit the value of having an industry standard content protection solution that is approved by most publishers and authors worldwide should not be underestimated. The platform also includes Reader Mobile Software Development Kit  (RMSDK) which offers developers core code libraries to build reading apps for desktop and laptop computers, and mobile platforms such as Apple iOS, Android, Blackberry and others. RMSDK also powers dedicated reading devices.

Much of the content read on these devices is free of DRM. This is because RMSDK supports PDF and EPUB, the two most popular open and standard file formats. Adobe Content Server (ACS4) is an important part of this ecosystem as well. It enables retailers to source content from a wide variety of publishers, distributors, and aggregators with a single, common fulfillment API, allowing retailers to offer a richer and more diverse catalog.

This is Just the Beginning

I sometimes hear folks who say essentially “Game over man!” when talking about ebooks—assuming that the Goliaths already have the ebook cat securely in the bag. To that I say: Wrong, wrong, wrong!

Certainly, there are real challenges for smaller retailers to compete in the digital landscape, but hard and impossible are two distinctly different beasts.

Brick and mortars can take a cue from B&N and leverage their direct customer interactions to move customers to their digital offerings. Another example in the U.S. is Hastings, a retail chain in the Midwest. Hastings has its own branded iOS and Android apps (powered by Bluefire Reader) and they sell an Android “Nextbook” tablet device (just $149) in their stores that comes pre-loaded with their branded eReading app and integrated store.

Small independents can work together to create shared solutions. A good example is the IndieBound apps and platform, operated by the American Booksellers Association. IndieBound offers a huge selection of ebooks and enables consumers to support their local neighborhood bookstore with their ebook purchases. I for one treasure my favorite local bookstore, Elliott Bay Books.

A Bright Future

We have a lot to look forward to in a broad and diverse marketplace for digital content. Here are a few other things I’m personally excited about:

Community Bookstores: I’m not talking about High Street communities here. I’m talking about communities based on common interests and lifestyles that are independent of geography. Communities around things like rock climbing, sustainable living, cooking, gardening, zombies and more. Ebook apps can be more than just places to read books—they can become a nexus for like-minded people.

Mobile app platforms have the power to easily integrate web-based content. When entrepreneurs combine the ability to manage and read a library of ebooks, with shopping, blogs, forums, feeds, social media and push notifications in a mobile app (centered around topics that people are passionate about) magic will happen.

Professional Development: I’ve always felt that ebooks are the best thing that ever happened to professional publishers. Why? In part because of the many ways professional publishers can take a community-building approach as described above.

But the huge opportunity is in the unprecedented insight that publishers can gain from the knowledge of how their content is actually being used — e.g., what do users search for, what chapter do they return to repeatedly, what do they bookmark and annotate? I could go on at length about this topic of analytics as I find it fascinating and incredibly promising, but for now we’ll leave it at that, except to say that while this may seem on the surface to be benefits that accrue only to the publishers, if you think about it, the resulting upsides for readers will be just as great.

New Business Models: Imagine services like Spotify, Rhapsody, or Netflix—but for books. The possibilities are endless.  It’s about innovation. ‘Nuff said.

Corporate Apps: Many of us don’t often think of the average enterprise as an ebook publisher or distributor. However, enterprises create tons (literally) of long format content for their employees, partners, investors and customers. Corporations also often buy commercial content in bulk and distribute it to employees.

The opportunities for corporations (or any large institution for that matter) to leverage ebook platforms with mobile distribution are immense—and unlikely to be fully addressed by the giant mainstream retailers. Ebook platforms will bring significant cost savings for corporations over print production and distribution, and will empower a wide variety of strategic initiatives: marketing, training, and standards compliance to name just a few.

One particular angle that is interesting is corporate ebook lending—as it relates back to those bulk content buys. And many of the points raised in my comments about Community Bookstores and Professional Development above play in here as well. Would corporations like to have insight into which of their documents were actually read (in part or in full) and by whom? I think so. As mobile devices play a larger and larger part of the global economy and in our lives, so will the pivotal role of digital documents in the workplace.

I could dive into libraries (e.g., as aggregators of regional content), or the revolution coming in education, and several other promising areas. But I’ll leave those for a different day.

So, Why Should I Care?

Well that depends on who you are. Are you an author? An educator? A publisher? Content manager? Librarian? Are you a bookseller, student or an avid reader? Do you simply want to make sure that consumers have as many choices as possible in where and how they get the media they care about? If you are any of those—and chances are, if you’ve read this far you fit one of those categories—you care about access, interoperability, choices, competition and innovation in ebooks. You understand the power of the written word and the responsibilities we in the industry have.

Don’t Drink the Kool-Aid

The Adobe eBook Platform is a useful tool for sure, but there are other important digital publishing technologies, and lots of new stuff is coming down the pike: ePUB3, watermarking, open publisher APIs, Windows 8, and more…  Our plan is to use the best tools available no matter who makes them.  That plan does not including waiting for the newest shiny objects, rather it includes using the tools and ecosystem available right here and now. Because there is one thing we can all be sure of—no one knows what tomorrow will bring.

– Micah

On the Adobe eBook Platform – Part 5 of 10: What is Adobe Vendor ID?

This is part 5 of a 10 part series by Micah Bowers, Co-Founder and CEO of Bluefire. Click here to read the first post in the series.

Adobe Vendor ID is a new solution from Adobe that is the most important new addition to the Adobe eBook platform since RMSDK. It enables eBook retailers to deploy branded ereading client applications that don’t require customers to have an Adobe ID in order to download ACS4 protected content.

With Vendor ID, customers can use the same username and password they use to log in to their account at the retailer’s website to authorize their client applications and devices. This greatly simplifies the user experience for consumers and also enables retailers to offer a single sign-in in for shopping, account access, and downloading—all working seamlessly with the Adobe eBook platform. The Adobe Vendor ID service is available to retailers through resellers such as Bluefire.

Have you ever used Adobe Digital Editions or a mobile app such as Bluefire Reader and been asked to authorize your device with your Adobe ID? This identity based DRM approach is useful because it enables interoperability of content acquired from a range of sources, across a range of commercial apps and devices. It also enables consumers to use neutral apps such as Adobe Digital Editions on the desktop, or Bluefire Reader on mobile devices, that are not affiliated with any particular retailer and thus do not include end user accounts.  These free apps provide a useful “Swiss army knife” function for ad-hoc documents and for reading content acquired from retailers and libraries that don’t offer their own ereader apps.

However, the requirement to have an Adobe ID to read an eBook purchased from a retailer or checked out from a library can also be a point of friction for the consumer. Before the consumer can download and read books they purchase or borrow, he or she must first visit the Adobe website and sign up for a free Adobe ID account. Consumers see this as an additional hoop to jump through, and this extra step can cause all kinds of confusion, including questions like “Who do I contact for support?”, “What is an Adobe ID?”, and “Why do I have to have an Adobe ID to buy or borrow eBooks from you?”

This friction has been one of the biggest challenges in the Adobe eBook ecosystem to-date for everyone involved. Vendor ID solves that. And, the great thing about Vendor ID is that it does not forgo the consumer benefits of interoperability.  Retailers who deploy applications that leverage Vendor ID can enable their customers to import and re-download content that they previously acquired with an Adobe ID,or another Vendor ID, and then read that content in the retailer’s branded application.  This removes one of the big barriers to acquiring new customers who have prior eBook purchases. And it offers a key point of differentiation from the closed, “private” ecosystems of the market leaders that trap their customers in their walled garden.

Retailers can now sell and deliver eBooks to the hundreds of millions of consumers with smart phones and tablets. They can provide the ease of use and convenience that consumers expect while providing consumers with greater freedom of choice. This is the kind of technology that can really change the game.

– Micah

On the Adobe eBook Platform – Part 4 of 10: What is the Reseller Model Anyway?

This is part 4 of a 10 part series by Micah Bowers, Co-Founder and CEO of Bluefire. Click here to read the first post in the series.

The software reseller business model is a model in which the developer of a technology product (such as Adobe) authorizes other companies to sell licenses to their products. The reseller has the ability to offer services and support that are related to those products. In the case of enterprise products, these authorized resellers are often focused on a particular, sometimes very narrow market vertical. Sometimes resellers are also “systems integrators” – offering integration services for the software they license.

This reseller model has a long history at Adobe, both in the packaged software sold via retail channels, and – more to the point here – in enterprise software. For example, the Adobe PDF Library is a Software Development Kit (SDK) that has been licensed via the reseller channel for many years. Licensees use the SDK to incorporate PDF functionality into their systems, often with the help of an Systems Integrator who has special expertise in PDF related software development. A similar model is employed by Adobe in a variety of verticals, such as education and government.

In the case of the Adobe eBook Platform, resellers provide important services such as consulting, support and systems integration that help retailers and publishers entering the rapidly evolving ebook marketplace make good strategic and technical decisions, while lowering overall costs and time to market.

Adobe announced the transition of their eBook Platform technologies to this reseller model on February 14th, 2011. They are working with a growing group of highly capable resellers with deep expertise in the digital publishing industry, including Bluefire. Products now sold through the reseller channel include RMSDK, ACS4, and Adobe Vendor ID. This switch to a reseller model takes time. It’s nearly a year after the announcement and the transition is still underway. Resellers are being added in new markets as demand warrants. The switch to a reseller model is indicative of a platform that is reaching maturity.

One downside of this transition is that it has at times caused some people in the ebook world to wonder whether Adobe is somehow “abandoning” the platform, as Adobe has transitioned their sales efforts to other areas and inquiries to Adobe about the products are referred to the reseller channel.  That is certainly not the case.  It is incumbent upon the reseller channel companies to promote the products they license, provide product information and deploy sales and support teams. We and others have been doing just that. The ebook marketplace is expanding so incredibly rapidly, with so many companies entering the market recently, that the bulk of our focus and energies have been spent on these new customers. We all have to get out and evangelize the platform to a larger audience.

Bluefire is aggressively pursuing our current business strategy because we believe that Adobe is actively supporting their eBook ecosystem. Supporting our belief is the fact that Adobe has continued to make significant enhancements to the platform throughout this transition. I described these enhancements in the previous post in this series. Adobe provides excellent support to the reseller channel and we talk directly to the developers and product management team at Adobe on a weekly basis. Based on this demonstrated history of support, it is my expectation that Adobe will continue to innovate in the digital publishing arena with solutions for magazines, newspapers and books. To learn more on what’s going on at Adobe visit

In my next post in this series I will look a bit deeper at Adobe Vendor ID which enables developers to create RMSDK based desktop and mobile apps that don’t require the use of an Adobe ID.

– Micah

On the Adobe eBook Platform- Part 3 of 10: What’s New?

This is part 3 of a 10 part series by Micah Bowers, Co-Founder and CEO of Bluefire. Click here to read the first post in the series.

In my previous post in this series I provided a concise overview of the Adobe eBook publishing platform. Many of you are probably already familiar with the basic elements of the Adobe ecosystem, but may not know about the following recent and exciting developments.

Adobe has released significant updates to RMSDK (versions 9.2 and 9.3) in the last year. Along with the usual fixes and minor tweaks, Adobe delivered a brand new EPUB rendering engine. While there are too many enhancements delivered as part of the new rendering engine to do it justice to in one short blog post, the most significant set of new features is related to foreign language support, notably Asian languages. There are also big improvements in typography and text rendering, including support for hyphenation and, importantly, support for text-to-speech (TTS) for content accessibility.

Adobe has also released Content Server 4.1.2 which enables what I call “pass-hash” protection for PDF and EPUB files. This pass-hash system is a new option beyond the “identity based” system that was already supported with the use of an Adobe ID account to authorize a limited number of devices. This pass-hash system embeds an encrypted (or “hashed”) version of a user name and/or password into the ebook file. Any user who receives a copy of the file and knows the username and password associated with the item can read the eBook. Adobe calls this a form of “Social DRM” because the eBook and password info can be shared with others and is not limited to a specific number of authorized devices. (Note that the release of this system does not imply a change to the concurrent device limit used in the more popular identity based DRM option.) Content Server 4.1.2 also added support for TTS as part of the available content protection permission set. More information on these topics can be found on the Adobe Digital Publishing Blog.

Adobe has also released a new generation of the Adobe Digital Editions desktop app, currently available as a Beta release in Adobe Labs. It has a very different look-and-feel than the first generation app, but the most important new feature is its integrated accessibility support. You can learn more about the latest release – “Adobe Digital Editions 1.8 Preview” which was released in November 2011. Download the preview and check it out for yourself! It is still a work in progress but this Beta is a good step forward.

That said, even as ADE improves I think many organizations will choose to release their own RMSDK based desktop applications. The reason for this is that desktop operating systems simply don’t enable a great way to “push” ebook file downloads from a retailer or library website into an application. So in order to offer a good consumer experience, the content acquisition interfaces need to be integrated within the applications themselves.

I believe this is a key reason why Adobe has focused so much of their development efforts toward providing enabling technologies to 3rd party developers – so that the 3rd parties can in turn build ereading apps and devices that tightly integrate discovery, download, and reading features.

The down-side of this focus on providing enabling technology is that it is sometimes “invisible” to a broader audience of folks in the digital publishing space – until companies like Bluefire build things with it.

A great example of this is another new capability of the platform: Adobe Vendor ID. This allows developers to create mobile and desktop applications that do not require that the end user have an Adobe ID. The user can simply “sign-in” to the ereading application with the user account they are issued by a retailer, library, employer, etc. This capability was first introduced in November of 2010, but companies have only begun to release their own products that take advantage of this capability in the last few months.

Another major change took place in 2011 as well: the transition of the eBook Platform to the “reseller” model. I’ll dive deeper in to that and Vendor ID in the next two posts.

– Micah

On the Adobe eBook Platform – Part 2: Overview

This is part 2 of a 10 part series by Micah Bowers, Co-Founder and CEO of Bluefire. Click here to read the first post in the series.

The Adobe eBook Platform is a set of technologies, applications, and web-based services that in total equate to an ecosystem for the creation, distribution, and display of rights managed digital content such as ebooks. There are many moving parts to this ecosystem, but one could vastly over-simplify it by describing itas an ebook publishing platform that any company or organization can leverage.

The notion that “any company” can use the Adobe eBook platform is a key element of what makes it different than other popular ebook platforms. For example, Amazon’s Kindle platform has a similar set of moving parts, but only Amazon can store, deliver and display the content in devices and applications created and controlled by the company. It is a private ecosystem that no other company can participate in, except as a “supplier”.

The Adobe platform allows many different kinds of organizations to participate. These organizations have the ability to participate either as end-to-end players that publish and deliver content directly to consumers, or as a company with specific industry vertical focus such as app developers, hardware manufacturers, retailers, and aggregators. These vertical players are as much parts of the ecosystem as are the individual technology components themselves.

Those technology components are:

  1. Adobe Reader Mobile SDK (“RMSDK”): This is a very deep set of C++ source code libraries that any organization can license and use to build ereading applications or ereader devices. A few companies have leveraged RMSDK to build their own applications, including Barnes & Noble, Kobo, Overdrive, and Sony, among others. However, developing a mobile or desktop application with RMSDK is a significant undertaking requiring a highly skilled team working for many months at the cost of hundreds of thousands of dollars. Because of these high costs, many companies turn to software developers that specialize in this area – such as Bluefire and a handful of others.
  1. Adobe Content Server 4 (“ACS4”): This is a server-side software product that is operated by hundreds of organizations around the globe. It encrypts ebook files and enables the operator to set permissions that control how the ebooks can be used. These forms of control manage  how much content users can copy or print, whether content can be moved to other devices, etc.  You could say that it “applies DRM”, though it does *much* more than that. A publisher might operate ACS4 themselves, or it might be operated by a distributor, aggregator, library, or retailer. The software supports ebook “purchase” models as well as loans, rentals and even subscription business models.
  1. Adobe Digital Editions (“ADE”): This is an ereader application for desktop computers. It provides a “neutral” platform for reading ebooks. It is neutral in that it is not associated with any particular retailer, publisher, or library. This is both a strength and a weakness. It is a strength in that many different ebook retailers feel comfortable delivering content to end users to read in ADE. Freely available, ADE allows retailers to avoid the cost of either licensing a white label app or licensing RMSDK and developing apps for multiple desktop operating systems (as Sony, B&N and a few others have done). The fact that ADE can not be customized is also a weakness because it does not enable retailers to integrate the shopping and ebook download features that consumers have come to expect – features that provide a much more seamless and intuitive experience.
  1. Adobe Web Services: There are several web-based services that Adobe operates 24/7 that make this whole ebook ecosystem work. These services include the Adobe Activation Service, which comes into play when consumers authorize their application with their Adobe ID or Vendor ID (I’ll discuss the ID system in detail in a later post). Another service is the Adobe License Signing Service which comes into play when a user is downloading a purchased or loaned ebook. Lastly, there is the Adobe Vendor ID service, which I will cover in part 5 of this series.
  1. Authoring: And of course there are the Adobe Creative Suite apps such as inDesign that everyone knows about and which are used to create the content in the first place. That said, one could create EPUB or PDF content in a huge variety of applications – including the most simple of text editors.

The Adobe ecosystem is a wide-reaching and mature ecosystem, and there really is no major competitor in the marketplace. That is not surprising as the investment of time and money required to build and maintain such an ecosystem is intense. Amazon and Apple have built their own versions of this in some ways, but these closed systems are in many ways “smaller” in scope because they don’t enable the direct participation of literally hundreds of other companies world-wide.

And, while the Adobe eBook platform enables so many organizations in the digital publishing ecosystem to build ebook businesses and services, there is also a key benefit to people who love to read: Choices. As a consumer, I can choose to buy ebooks from a host of different companies world-wide, both from major retail chains and small indie bookstores or publishers. I can choose to read that ebook on a wide variety of ereader devices from one of many established hardware brands, or read it with any one of dozens of ereading applications  available on just about any smartphone, tablet, or computer, including apps developed by Bluefire. And I get to actually keep my own ebook files and mange my own collection instead of having them managed in a closed system. I can back my files up, put them on a thumb drive, and so forth. For me personally, this  control has always been essential.

In part 3 of this series: “What’s New?” I will describe the many improvements that have been made to the platform recently.

– Micah

On the Adobe eBook Platform – Part 1: An Introduction

This is the first of a 10 part series where I will talk about my perspectives on the Adobe eBook Platform. I’ve noticed that while the platform is broadly used internationally by publishers, retailers, distributors, device makers and libraries – not to mention many millions of consumers – there is not a whole lot of in-depth discussion and coverage on it to be found online. My goal in this blog is to help fill that void a bit, start a conversation with our peers, and to advocate that those of us that participate in this ecosystem make renewed efforts to cooperate and work together. We need to work together for our collective benefit and for the benefit of the most important people to us all: the people who read.

This series will be focused on the business and technical side of things, so probably of interest mostly to folks who work in the digital publishing space. Here’s an overview of the topics I’ll be hitting on:

  • Part 2: Platform Overview
  • Part 3: What’s New?
  • Part 4: What is this Reseller Model Anyway?
  • Part 5: What is Adobe Vendor ID?
  • Part 6: Why Should I Care?
  • Part 7: But Doesn’t DRM Suck?
  • Part 8: Resources and Players
  • Part 9: What Does the Future Hold?
  • Part 10: A Call to Work Together

To provide context for the subsequent posts in this series, here’s a short introduction to me and my company, Bluefire:

I’m Micah Bowers, the CEO of Bluefire Productions, an independent software company in Seattle. We offer digital content distribution tools for retailers, publishers, libraries, and anyone else who has high-value content that they’d like people to read, and with whom they’d like to build a deep and lasting relationship.

Our core products today are “white label” (customer branded) ereading applications for smartphones and tablets.  These apps support PDF and EPUB documents as well as Adobe’s ebook DRM. Our current customers include Books-A-Million, Hastings Entertainment, Mardel Christian & Education, the American Booksellers Association and Kaplan Publishing, along with many others in the U.S., Canada, Europe, Asia, Latin America and South America.

You can learn more about Bluefire and our services by visiting our website at For those that are already familiar with us, you might want to check out this recent blog post that explains what we’ve been up to the last couple of years. For my personal background, you can look me up on LinkedIn here.

While it probably goes without saying, I do want to be clear that my comments here on this blog are my own personal perspectives, and in no way reflect the views of Adobe Systems Inc.

It also goes without saying that I’m far from impartial on this topic as these technologies sit at the core of our products.  That said, my intent here is to avoid simply being a cheerleader for the platform, and to instead provide useful information and personal perspectives on the technologies and the role they play in the overall digital publishing landscape.

– Micah

Hello (Again) World

Wow, three years have gone by since my last blog post. It has been quite a journey.

That last blog post was in January 2009. At that point we at Bluefire had been working closely with Adobe for a couple years on a substantial overhaul of their ebook platform. At that point, Adobe Digital Editions had been available for about a year and Adobe Content Server 4 had been out for a few months. Sony had recently become the first major ebook retailer to adopt the new Adobe eBook Platform.

In February of that year Adobe released the Reader Mobile Software Development Kit (“RMSDK”) and it took off like a rocket ship. Many hardware companies built ereader devices using RMSDK, and key industry players leveraged the platform including Barnes & Noble, Kobo, Overdrive, Ingram, and Google – among many, many others.

As 2009 progressed we continued to work with Adobe on building out components of the platform and worked with several other clients in the digital publishing space. A lot of our client work that year was focused on developing technologies for browser-based reading systems.

By the end of 2009 my partner Patrick Keating and I recognized an unmet need in the market: mobile ereader apps. Yes, any company could license RMSDK and build their own app, but that process is a time consuming and expensive proposition that requires skill sets that are still very hard to find. We recognized that this skills gap represented a big opportunity for us because we were intimately familiar with the technology, and because, after many years working in the ebook space, we had been bitten by the ebook bug. We believed that many retailers, publishers, and libraries world-wide would be interested in deploying their own mobile ereader apps. Even large companies and institutions that we don’t necessarily think of as being in the “book” business seemed to be likely candidates to want to distribute long format content to their employees, investors, partners, and members on mobile devices.

So, after 8 years working as a boutique UX design and development services firm, Patrick and I decided it was the right time for us to reinvent Bluefire as a digital publishing platform provider. Our initial goal was to create a “white label” mobile app development system that would enable us to deliver customer-branded ereading apps to retailers and publishers so that they in turn could distribute ebooks directly to their own customers under their own brand. The idea was to “level the playing field” so that lots of new retailers and publishers could enter the rapidly evolving ebook marketplace quickly and affordably.

In the fall of 2010, after many months of hard work, we delivered our first white label iOS app to Books-A-Million, one of the largest brick-and-mortar retail chains in the US. In early 2011 we became an authorized reseller of Adobe eBook Platform technology licenses and services. And in August of 2011 we began delivering Android ereader apps to our customers as well.

I’m pleased to report that today, just one year after releasing our first product, we have over 75 enterprise customers in 18 countries and that Bluefire is entering 2012 as a growing, profitable and 100% independent company.

All of us here at Bluefire are looking forward to what should be an eventful and exciting year.

– Micah