Subcompact Publishing tools are first and foremost straightforward.
They require few to no instructions.
They are easily understood on first blush.
The editorial and design decisions around them react to digital as a distribution and consumption space.
They are the result of dumping our publishing related technology on a table and asking ourselves — what are the core tools we can build with all this stuff?
They are, as it were, little N360s.
I propose Subcompact Publishing tools and editorial ethos begin (but not end) with the following qualities:
- Small issue sizes (3-7 articles / issue)
- Small file sizes
- Digital-aware subscription prices
- Fluid publishing schedule
- Scroll (don’t paginate)
- Clear navigation
- HTML(ish) based
- Touching the open web
Many of these qualities play off one another. Let’s look at them in detail.
Small issue sizes
I’ve written quite a bit about creating a sense of ‘edge’ in digital space. One of the easiest and most intuitive ways to do so is to limit the amount of data you present to the user.
It’s much more difficult for someone to intuit the breadth of a digital magazine containing twenty articles than a digital magazine containing, for example, five. By keeping article number low this also helps decrease file size and simplify navigation.
Small file size
Speed is grossly undervalued in much of today’s software — digital magazines inclusive. Speed (and with it a fluid and joyful user experience) should be the thing you absolutely optimize for once you have a minimum viable product.
One way to bake speed into a publishing product is to keep issue file sizes as small as possible. This happens naturally when you limit the number of articles per issue.
Reasonable subscription prices
Ideally, digital subscription prices should reflect the cost of doing business as a digitally indigenous product, not the cost of protecting print subscriptions. This is yet another advantage digital-first publications have — unlike print publications transitioning to digital, there is no legacy infrastructure to subsidize during this transition.
Fluid publishing schedule
With smaller issue sizes comes more fluid publishing schedules. Again, to create a strong sense of edge and understanding, the goal isn’t to publish ten articles a day, but rather to publish just a few high-quality articles with a predictable looseness. Depending on the type of content you’re publishing, days can feel too granular, and months require the payload to be too large. Weeks feel just about right in digital.
Scroll (for now)
When I originally presented these ideas at the Books in Browsers conference in 2012, the dismissal of pagination was by far the most contentious point. I don’t mean to imply all pagination is bad. Remember — we’re outlining the very core of Subcompact Publishing. Anything extraneous or overly complex should be excised.
I’ve spent the last two and half years deconstructing scrolling and pagination on tablets and smartphones. If your content is formless, then you might be able to paginate with minimal effort. Although, probably not.
Certain kinds of pagination increase the complexity of an application by orders of magnitude. The engineering efforts required to produce beautiful, simple, indigenous, consistent — and fast — pagination are simply too high to belong in the subcompact space.
Furthermore, when you remove pagination, you vastly simplify navigation and thereby simplify users’ mental models around content.
No pagination is vastly superior to pagination done poorly.
Navigation should be consistent and effortless. Subcompact Publishing applications don’t require complex how-to pages or tutorials. You shouldn’t have to hire a famous actor to show readers how to use the app with his nose. Much like a printed magazine or book, the interaction should be intuitive, effortless, and grounding. The user should never feel lost.
By limiting the number of articles per issue, and by removing pagination, many of the routes leading to complex navigation are also removed.
When I say HTML I also mean EPUB or MOBI or any other format with an HTML pedigree. HTML has indisputably emerged as the future format for all text (and perhaps also interactive) content. By constraining Subcompact Publishing systems to HTML we bake portability and future-proofness into the platforms. We also minimize engineering efforts because most all computing devices come with high-quality HTML rendering engines built in.
Simply: whatever content is published on a tablet should have a corresponding, touchable home on the open web.
Content without a public address is non-existent in the eyes of all the inter-operable sharing mechanisms that together bind the web.