A consumers thoughts on eBooks

With the release of iBooks 2, and Apple’s digital textbook initiate, they have, once again, made a technical decision that a lot of people are unhappy about. Like another technical decision that Apple made, Apple has made a decision that, unsurprisingly, is in their own best interests.

In his article, Ed Bott is claiming that Apple is deliberately trying to break the ePub standard in favor of it’s own, proprietary version.

In a well balanced response, John Gruber proposes that:

“The only people who seem to be confused about iBooks Author’s relationship to ePub are technically-minded people who know exactly what ePub is and who have a vested interest in seeing the open standard become the de facto industry standard.” 

Given their stance on secrecy, we will likely never know Apple’s internal view on this, however, I would like to propose that, from a consumer’s point of view, ePub is already a broken standard.

If ePub was a true, open, embraced standard, then, as an end user, I would be able to open any book that I have purchased on any client, or device of my choosing. So, I should be able to buy an book from Apple and read it on a Kindle, or buy a book from Amazon and read it in iBooks.

Currently, Amazon does not use ePub, and Apple’s iBooks utilize a version of their FairPlay DRM, rendering each book locked to the retail platform on which it is purchased.

“An EPUB file can optionally contain DRM as an additional layer, but it is not required by the specifications. In addition, the specification does not name any particular DRM system to use, so publishers can choose a DRM scheme to their liking. However, future versions of EPUB (specifically OCF) may specify a format for DRM.”

via Wikipedia

As a consumer, unless I want my books scattered across different reading applications I am forced to either buy all my books from a single retail source, effectively locking me in, or going through some ethically dubious and probably illegal process of removing the DRM from the books. (There are some exceptions such as O’riley who provide DRM free, standard ePub format books).  

As a consumer don’t I deserve a better solution than this?

As the TV and Movie industries constantly prove, retailers don’t necessarily have consumers best interests in mind, and this will, most likely, prevent there from ever being a true, open standard. 

So is Apple wrong, well yes and no. As a developer, on the leading edge, standards are simply a handbrake on innovation, and any developer should be able to add new features, with graceful degradation, allowing most of the content to still work on older clients without the new features. It is then up to the standards bodies should then adopt and incorporate the new features as they become popular.

Fast forward twenty years into the future can we assume 90% of all books and magazines are sold digitally, using a true open, DRM free standard?

Maybe we need to change how we think about things. Are Amazon and Apple the new publishers? Are the old publishers now simply the content owners, editors, author’s agents, marketers and publicists? 

An alternate view is that why should there be some man in the middle at all when I could buy directly from the publisher, or the author themselves online? Other than discoverability, and devices, what value will retailers like Apple of Amazon add?

One thing I know is that business is business, and my guess is that the truth is now somewhere in between. If I was a publisher, I would be looking how to sell directly to my customer, and if I was a retailer, I would be looking to lock in as many customers as possible to my end-to-end system.

My new years testing resolutions

Eric Jacobson blogged about his resolutions for 2012. At his prompting, and because I am in a reflective mood and thinking a lot about my career now that I am currently looking for work again. So, here are my 2012 new years testing resolutions.

New years tester resolutions

  • Get a new job at a great company that cares about quality and testing or start my own that does.

  • Write a magazine quality testig article at least once a month.

  • Turn my back on .net and visual studio and widows and fully embrace ruby, rails and selenium.

  • Launch an application in the Apple app store.

  • Develop and deliver a test training course.

  • Deliver a new testcast each fortnight.

  • Present at a testing conference like I did at ignite last year.

  • Write a book.

Browser compatibility testing

The goal of browser compatibility testing is to ensure that the site renders without error on the target web browsers. Some minor rendering differences are expected from browser to browser, or within different versions of the same browser.

The image below shows the rendering differences between Internet explorer 5.5 (which is ghosted) and Internet Explorer 6 for Microsoft’s homepage, in December 2008.

MicrosoftDotCom.jpg

What you can clearly see is that the main page elements in IE5.5 are clearly moved to the left. You can also see that the navigation bar is not working at all, and that silverlight is not supported on IE 5.5.

These types of rendering differences will occur typically across major versions of browsers, but as the same rendering engine is typically used on all platforms for multi-platform browsers, the same version of the same browser will typically render the same result on all platforms that it supports. This reduces the need for testing the same version of a browser on multiple platforms, however simple sanity checking of browsers cross platform is recommended if the configuration is already available.

So which browsers should I test?

To determine where you should focus your testing effort, let’s look at the browser market share.

BrowserShareDec08.png

Source: http://en.wikipedia.org/wiki/Usage_share_of_web_browsers

Generally a browser should be tested if it meets one of the following criteria:

  • It is used by a significant portion of a sites users, and is in common, widespread usage.
  • It is the default browser on the latest version of Windows or Mac OS X.
  • It is a newly released browser which is expected to quickly gain a significant portion of browser market share, e.g. the latest IE, Firefox or Google Chrome

After reviewing the data against those criteria, the following browsers are suggested for inclusion for testing most sites:

Browser

Reason for inclusion in test matrix

Internet Explorer 8.x Most common browser in use today.
Internet Explorer 6.x Second most common browser in use today.
Firefox 8.0 Latest version of Firefox
Safari 5.x Default browser on Mac OS X.
iPhone & iPad Uses webkit, the largest single mobile browser.
Google Chrome (latest) Chrome has significant, rising market share

What bugs am I likely to find?

To decide what we need to test we need to understand what is likely to break. The current batch of web browsers have a set of commonly known bugs and differences. If you understand these differences, you can go a long way to understanding why pages render differently in different browsers. Internet explorer has a large number of CSD layout issues and rendering bugs. A full list is available here.

You can see visually how these bugs manifest themselves with the Acid 2 test. This is a test that is designed to see if a browser can render CSS correctly.

With its market dominant position, most sites will be built for Firefox first, and as a result, if not tested, other browsers will now have layout issues. This is clearly shown below in this comparison of different browsers running the browser Acid 2 test.

BrowserAcidTest.png

If your sites are developed on Macs, you can almost guarantee there will be issues in internet explorer. If your site is developed on Windows, the opposite applies and Safari, Chrome, Firefox and IE6 will probably be broken.

One more thing

Your site will never look the same in EVERY browser. It is simply not possible. Here is how microsoft.com looks in lynx.

MicrosoftInLynx.png

Ironically, this is exactly how search engines see the world.