Skip to main content

You can't take sides!

We spend a lot of time explaining ourselves to funders and prospects. In one of our first "real" presentations we were describing why readers will get better value from the improved reading experience of Tizra sites, and publishers will be attracted by that superior usability combined with really flexible and sophisticated selling and management tools. Someone jumped right in at that point and asked "whose side are you on, publishers or readers?" I tried to "unask the question" and say that we were on both sides, but was greeted by a flat contradiction -- "You can't be on both sides you have to pick who's more important." This dichotomy of sides seems to contaminate a lot of thinking in the "content industries", and it's fundamentally flawed. Simple economics gives the answer: Publishers and customers are fundamentally on the same side. The publishing industry generates value for readers, who pay for that value via the market. Of course there is tension: Publishers want to optimize their income and cost. Readers want find the lowest price that gives them the value they require. But almost by definition, a publisher's best interest is aligned with the needs of their customers, the readers. That means that user interaction is critical as is selling the most useful information package and helping people find stuff easily. More flexible marketing tools don't just improve publisher returns, but create user value by letting publishers make better products. The biggest place this goes wrong is in the area of DRM and piracy. Not every potential reader will be become a customer. Unethical potential readers may even become pirates. The thing to remember is that pirates are not customers, and many may not even be potential customers. I don't have unrealistic ideas about fraud, piracy, and value delivered. In over a decade of web site building and hosting, I've seen my share of piracy problems that have had to be solved. But almost every guard against piracy inconveniences readers, and reduces the value delivered. Detecting piracy is also usually pretty easy, because serious piracy has to steal a lot of data, and that's something that can be detected by a computer. I'm happy knowing that our selling tools are helping readers to buy information at the granularity that best meets their needs. I'm also happy that by encouraging publishers to think first of customers, and only secondly about potential pirates, I know we are representing the interests of both groups, and that trying to make the reader experience better is a great way to help publishers find customers.

Comments

Popular posts from this blog

Technical Podcasts

If there is something the web as surely changed, it was the way that software engineers need to work. It is now a crucial aspect of our work to be able draw from the huge internet knowledge base out there in an efficient way to get to the right answers. Part of that information extraction is related to the keeping-up-to-date effort that every developer is required to accomplish to continue to be productive. While previous a software engineer could rely mostly on print material, nowadays we need to rely as well on content available on the net. Podcasts are such a source that can bring an amazing amount of information to the mix of knowledge one needs these days. If you are a software engineer and have not jumped into the podcast wagon yet, I suggest you do so. Here is a list some technical podcasts that we hear at Tizra: The Java Posse : a fantastic podcast on Java development. Containing news info update, analysis of tools, overall software development discussions. Software as She Dev...

Using XML to Create a Better Online Reading Experience for the American Payroll Association

Congrats to the American Payroll Association on their recent launch of XML-based publications on Tizra!  Thanks to this collaboration, APA's authoritative books for payroll professionals are now available in crisp, reflowable HTML, creating a user experience that feels like a truly digital native product, rather than a conversion from print. XML-based publishing also creates a better mobile reading experience, supports more precise search and navigation, and opens the door to better accessibility for users with low vision and other disabilities. Our partners at  Scribe  did a great job supporting APA through the process of producing the XML for loading into Tizra, and we’d definitely recommend them to anyone interested in such a transition. It’s hard to overstate what a big step forward this is for Tizra as a platform and a company. XML has long been planned for in the product's architecture, but now for the first time, we have a working example that demonstrates t...

The importance of continuous integration

Leading a team of developers in the effort of building a robust, quality software product should involve the establishment of some process and tools to assist the team effort and serve as a safety net for the errors of getting people to work together. Continuous integration is, I believe, a crucial element of that process. Introduced by Martin Fowler and Matt Foemmel (see article Continuous Integration ), continuous integration establishes the practice of frequent integration of work developed by the several team members verified by automated build and testing of integrated code within a clean sandbox. This practice is valuable for several reasons: It promotes the development of a clear process of building/deployment independent of any specificity of developer's platforms. Code that exists on a single platform only is bound to become dependent on specific aspects of that platform without anyone really noticing the dependencies until trying to port to other platforms. The existence ...