Publishing for tablets – A market ripe for disruption

Home » Blog » Business » Publishing for tablets – A market ripe for disruption

This week there were two quite intriguing posts on 37signals’ Signal vs. Noise blog:

Tablets are waiting for their Movable Type
Publishers shouldn’t be app developers

Both posts deal with the shortcomings of magazine and newspaper publishing for tablets like the iPad. Currently, publishing for the iPad and other tablets mostly amounts to magazine publishers writing native apps that wrap their content. Given that magazine publishers usually don’t specialize in software development more often than not this entails slow, unstable apps and a generally less than stellar user experience. You might object that there’s Newsstand for iOS, which is supposed to be a standard way for presenting and subscribing to magazine content on the iPad. However, Newsstand actually is nothing more than a glorified iOS folder that still contains ordinary apps.

DHH properly summarizes the sorry state of magazine apps:

These magazine apps completely suck, generally speaking. They suck in the same ways that the CD-ROM rush of the 90s sucked. They suck for all the reasons poorly written native software sucks: They’re slow, they crash, they get stuck.

Ryan makes an interesting point by likening publishing for tablets as of today to web publishing pre-2000:

Remember the web before Movable Type? If you wanted a blog you had to program one. You had to know databases and webhosts and PHP or Perl. If you were “just” a web designer, or a writer with ideas, you had to hire an in-demand web programmer to make it happen. Publishing was expensive and hard.

Before blogging platforms like Movable Type or WordPress publishing for the web boiled down to manually cooking up a database-driven website in a common programming language like PHP or Perl or using a fairly complex CMS that required quite some technical knowledge. Back in the day, web development still was somewhat in its infancy and there were none of those awesome frameworks like Ruby on Rails that greatly simplified and standardized web development. The whole process was error-prone, tedious and complex.

Ryan continues to suggest that what tablet publishing might need right now is a standardized platform similar to blogging platforms for the web:

Now is a great time for another Movable Type. Writers would love a way to push serialized content straight to tablets, and the experience would be a boon to readers. Tablets are the best way to read, and Newsstand is the equivalent of RSS for non-geeks. Hopefully apps like The Magazine inspire somebody to make this happen.

I couldn’t agree more.

However, there’s another exciting aspect to these blog posts. They both sport the underlying theme “Content publishing for tablets sucks!“.

When linking this theme to Jason’s post from earlier this month wherein he outlines how 37signals lately has been pruning its product line in order to make room for new, soon to be announced products the big picture is: 37signals will soon launch a novel tablet publishing product and right now they’re setting the stage.

Considering their pretty impressive publishing history with Signal vs. Noise, Getting Real and REWORK this makes a whole lot of sense, especially considering their “Scratch your own itch” mantra.

I’m quite sure we’ll be seeing such a publishing product by 37signals pretty soon and given their track record this product might very well disrupt the market for tablet publishing solutions.

In the meantime, you might have a look at these promising tools and services that help you with publishing for tablets and and various eBook formats:

Leave a Comment

* Checkbox GDPR is required


I agree

By continuing to browse the site you agree to our use of cookies. Privacy Policy

Privacy Preference Center

Strictly necessary

These cookies are necessary for the site to function.

PHPSESSID: Preserves user session state across page requests.

__cfduid: Used by the content network, Cloudflare, to identify trusted web traffic.



Remembers the user's submitted data when a comment is submitted in a blog post. The purpose is to aut o-populate form fields for subsequent comments, in order to save time for the user.



Statistic cookies help us to understand how visitors interact with our websites by collecting and reporting information anonymously.

_ga: Registers a unique ID that is used to generate statistical data on how the visitor uses the website.

_gat: Used by Google Analytics to throttle request rate.

_gid: Registers a unique ID that is used to generate statistical data on how the visitor uses the website.

collect: Used to send data to Google Analytics about the visitor's device and behaviour. Tracks the visitor across d evices and marketing channels.



We use Wordfence to secure our website against hacking attempts:


Close your account?

Your account will be closed and all data will be permanently deleted and cannot be recovered. Are you sure?