DriveThruRPG Phone PDFs Review

Role-playing games are a delightfully analog hobby; the best parts of coming together with your friends to roll dice and tell stories cannot be duplicated by digital media. The way we play, though, has changed, with forums and voice chat programs and online dice rollers all giving us ways to use technology to enhance the RPG experience. When it comes to the actual reference materials, progress has been uneven. Online SRDs and paywalled content providers like D&D Beyond show we at least acknowledge that digital reference materials can look different, but the majority of game PDFs out there are just books, barely improved from the days when RPG PDFs were made with a scanner.

DriveThruRPG’s latest experiment, done in conjunction with a few major developers, is to push the bounds of the PDF format by producing RPG sourcebooks designed to be used on phones. These PDFs are made to be easy to read and easy to search, using extensive linking and small page formats to avoid eye strain. The idea is a good one: more devices that can be used at the table means more players who have copies of the rules, easier lookups, and generally smoother play sessions. The actual documents being released are also quite good, for the most part. However, the execution of the new format has revealed some vulnerabilities, both in the use of these documents themselves and what their design tells us about the state of the digital RPG rulebook.

RPG PDFs in General

PDF stands for portable document format, and was originally developed in the 1990s as a way to send documents that could be viewed and printed on any computer in a consistent manner. Most word processors store things like fonts and images external to the documents themselves, meaning that having a file format which contained all the media necessary to open a document was a serious innovation. The format’s design had two main consequences: first, everyone was able to freely acquire software to read (but not write) PDFs, and second, it was technically trivial to create a document which was a sequence of full-page images, making PDF the de facto standard for digitizing scanned physical documents.

As you may guess, PDF is showing its age; the format is over 25 years old and the codebase it uses is even older than that. While PDF is a flexible format, getting the files to open and scan smoothly takes a fair amount of optimization work. This is improving a bit; PDF was standardized in 2008, so changes to the feature set have slowed. That said, making a bulky PDF is easy, and making a lean one less so.

RPG PDFs mostly started as scanned books, with some early adopters like BTRC and Steve Jackson Games selling digitized games in the early 2000s. The first digital GURPS PDFs from Steve Jackson were basically the laid out books exported into PDF, which was a drastic improvement over scanned books but still not ideal for the format. Unfortunately, even 15 years later this is still the standard: most PDFs are generated directly from book layout files and then populated with links and bookmarks. If we’re lucky, there are layers which let you turn off background art.

The awkwardness of basically reading a book on a computer or tablet brings me to my first gripe with the Phone PDF paradigm: we should be designing PDFs better, period. While the individual Phone PDFs are variable in execution, they’re all designed with consideration made for the device that will be used to read them. As someone who does most of their PDF reading on a device which is pretty much as close as possible to the book format (a full-sized touchscreen tablet), I’m still annoyed at how little is done to make PDFs more usable.

So the entire “RPG PDF” standard is a bit archaic in my opinion. Still, PDFs designed for phone accessibility represent a solid step towards making digital gaming materials easier to use. Sort of. When DriveThruRPG and their partners took aim at phones, they took aim at a digital ecosystem they were woefully unprepared to enter.

Getting the PDFs on my Phone

The DriveThruRPG library app sucks. There, I said it. It wholesale sucks, I do not wish it upon anyone. The login process is utterly retrograde; you must generate a long hexadecimal code and then copy it into the app. To do this, you either have to access the site on a larger device and type on your phone very carefully, or access the site on the phone to copy the key, which is terrible because the site isn’t mobile optimized. Then, when you actually get into the app, you’ll find that it only works in landscape mode because it’s designed for tablets. Also, the actual library and download management is a) not better than just using the website, and b) not better than either Android or iOS’s filesystem. So where do we start with the phone PDFs? With having no worthwhile environment to get them onto your phone.

I downloaded the files onto my computer, uploaded them to Google Drive, then downloaded them again to my phone. Then I had to open them. The native Android PDF reader doesn’t support in-text links. With my default choice unable to load the core functionality of the PDF, I downloaded Foxit Reader. Foxit Reader for Android is good, but on my two year old Moto G5, it’s pretty stuttery. Nonetheless, the links were usable, the PDFs were clear, and if I could accept the jerkiness of page turns, it was at the very least workable.

So we have no software support, no consideration of operating environment, and a really uneven level of optimization (more on this later). Without even trying to use the PDFs, we’re off to a rocky start. While DriveThru’s library system for computers is at least passable, for phones it truly is not. Now, there are plenty of ways to make it work; an ebook library manager would probably be perfect for this task. But we’re now asking users to have three third-party apps (a full-featured PDF reader, some form of cloud file manager, and an ebook library manager) to get a smooth Phone PDF experience on an Android phone. Before we’ve even opened a single file, I can declare this experiment half-baked at best.

Using the PDFs

So getting the PDFs onto my phone was a chore. Once they were on there, though, and I had Foxit installed and had ensured that the links actually worked, it was time to try out some PDFs. I was able to scare up three for a round of testing: Zweihander, which I received due to my ownership of the Zweihander core rules, Pugmire, which DriveThruRPG released for free as part of a Phone PDF promotion, and Masks, which Cannibal Halfling opted to buy due to our illustrious history with the game. While I did not pay for all of these PDFs, Pugmire was available for free and Zweihander was available pay-what-you-want when it came to the Phone PDF format. Considering how this article goes, though, you may be able to guess that none of the publishers are paying me.

Zweihander

screenshot_20191014-182216

Zweihander had, out of the three PDFs, the smallest font size. That said, the layout of the Zweihander book is excellent, and it translated well to the one column phone PDF, with breaks and headers making the text easy on the eyes despite its small size. Unfortunately, Zweihander was the most technically problematic. As you can see from the screenshot, the PDF has two navigation panes; the one on the bottom that gives a ‘back’ button and a link to the table of contents, and a vertical pane on the right which in theory points to different entries in the index. I say in theory, because none of the links on either of these panes worked. My guess is that a fix will be coming shortly, either because someone else has already said something or because I’m saying something right now. Nevertheless, while I like navigation panes I can’t really recommend one that doesn’t have any usable links in it. The evidence that this marketing campaign may have been rushed continues to mount; we’re missing both a good app environment and adequate QA. Another issue which carries over to a degree from the full-size Zweihander PDF is the massive file size; the Zweihander PDF was 90MB while the other two were both less than 20. While the page count is nearly triple that of Pugmire, the file size is triple that over again. I noted the relatively large size of the Zweihander PDF back when I got the game originally and shrugged, but dumping a large PDF into your computer’s RAM is a lot less onerous than doing it on your phone. 

Pugmire

screenshot_20191014-182436

The Pugmire PDF had working links, you can just barely see the blue boxes that Foxit uses to highlight them in the screenshot. The font size is larger than Zweihander, though Zweihander is a bit better laid out than Pugmire both in phone and in original formats. On the sample page, though, you can see how Onyx Path was able to incorporate sidebars in their one-column format, and the relative abundance of links. I found that Pugmire had the most issues with wall-of-text pages, both due to weaker breaks and format changes than Zweihander as well as what appears to be less abridgment from the original text. While Pugmire used the most art from the original book, I found it to be more distracting here; Zweihander’s black and white line art was meshed with the formatting better and Masks’ cartoon-style art both scaled down better and was used more judiciously.

Masks

screenshot_20191014-182315

Masks is the winner here format-wise; the high-contrast layout works better on a small screen. The two navigation buttons on the bottom work, and lead to what is the best part of the Masks PDF: In addition to a table of contents, Masks employs a number of hierarchical pages that let you browse by topic instead of having to read through the table of contents in page order. It acknowledges that Phone PDFs are more likely to be references than documents which someone will actually read cover to cover. While this mode of displaying topics in the PDF adds a number of pages, Masks was not appreciably larger than Pugmire at 15 MB. Masks also appeared to work the smoothest on my phone, though that could have been equally due to the graphical contrast as the loading time.


With the exception of Zweihander, all the PDFs worked fine, and the Zweihander PDF will also work fine once the link issue is fixed. I didn’t particularly enjoy using my phone to read rulebooks in any of the three cases, but these PDFs are a perfectly usable reference guide for the game table, and will help immensely for a gaming group who doesn’t use laptops or tablets. I don’t think there’s enough of a value-add here to make any of these worth additional money over the price of a rulebook; I’d gladly take one alongside buying a full rules PDF but not pay extra. The biggest problem with these is they simply don’t work well enough for the people who would actually derive utility from them. As a gamer with disposable income, I purchased a convertible tablet instead of a standard portable laptop because I knew I’d use it for PDFs. Anyone who has a few hundred dollars to spare can buy either a tablet or a convertible Chromebook like I did. The people who currently buy phones that will actually display these PDFs smoothly, iPhones and up-to-date Samsung Galaxies and the like, also have enough money to just buy a tablet. If you really couldn’t afford a tablet, you’d be working with something much closer to my Moto G5 than a top-tier phone, and on my phone this PDF experience is something you endure, not enjoy.

So what did I learn from this experiment? Well, the work that went into making these PDFs and making them readable is worth noting. The optimization isn’t great, but there’s a certain point at which that’s Adobe’s fault, not the designer’s. Some of these innovations, like built-in navigation and hierarchical browsing, should be part of all PDFs, not just phone PDFs. Fact is, even among companies known for great layout, PDFs are just digital books. If we want RPGs to be more usable on electronic devices, digital book shouldn’t cut it. If there’s one takeaway I have from these Phone PDFs, it’s that for every device, be it a phone, tablet, or computer, RPGs could be doing better, but aren’t. Whether its print incarnation is a big hardcover, a 6×9 softcover, or even a damn zine, there’s a whole lot of room to do way more with the presentation and accessibility of digital RPGs. Phone PDFs may be imperfect steps forward, but they’ve cracked open a door, and reminded us that we could be doing so much better than reading a book on a screen.

6 thoughts on “DriveThruRPG Phone PDFs Review”

  1. xpost from reddit:

    Hi, I’m Thomas, the guy who did the phone pdf translation for Masks: A New Generation. Thank you for your kind words regarding the product. (Especially the hierarchical navigation!)

    One clarification to your review I’d like to make is while the “by topic” navigation in Masks does add on a few more screens, it only added sixteen more in a product that had 774 screens.

    Overall, these books seem to generate screens (“pages” doesn’t feel like the right word here) in the hundreds. Masks is a 208-page digest-sized book with very few tables and small statblocks. I’d imagine a US Letter/A4-sized book like Eclipse Phase or The Expanse would wind up with about 1,400 to 1,500 screens. My own small games (the four vs. games on that page) translated to four US Letter-sized pages, which ranged from 43 to 46 screens. (vs. EMPIRE is only 24 screens as it doesn’t have an expansion.)

    Like you, I’m not certain if a full rpg book needs to be in Phone PDF format. Thinking about it, if I were a company with a large book, I’d treat this format as more of an extended GM screen with limitless panels than translating all of a book like Pathfinder 2 to fit a phone. Use hierarchical navigation like we did in Masks to get you to the references you need with a few taps on the screen. Translating a 640-page book like Pathfinder 2 to this format would result in at least 4,000 screens. For a small game like vs. MIRRORSHADES, the format is really nice. (Also at DriveThru, getting a copy of any of those vs. games gets you the game in three different pdf formats.)

    Again, thanks much for looking at the format and the kind words about Masks. If you have any questions about developing a game in that format, I’d be happy to answer!

    Liked by 1 person

    1. Thanks for reaching out! As a point of comparison, the Zweihander Phone PDF had slightly over 2000 screens, and Pugmire was around 750. Pugmire is fairly comparable to Masks (~250 pages, also digest), and indeed the two products had similar levels of compression, with Masks slightly less compressed (and as you saw in my review, likely better for it). As Zweihander is a roughly 700 page full-sized hardcover, the degree of compression is impressive, and was achieved through a combination of small font sizes, abridgment, and smart layout.
      Speaking of good layout design, I feel the need to mention that I was a backer of vs. Kickstarter and was immensely impressed by the physical products I received. I’m glad to hear there’s more demand for that sort of design talent in the RPG space!

      Liked by 1 person

      1. With Masks, we compressed the images to 300 ppi, even though the document from DriveThru asked for 144 or 150. But even at that size, the artwork looked too rough. The vs. Kickstarter games all had Phone PDF versions added — if you downloaded them as part of your backer rewards from the last campaign, the phone versions have been added to your downloads at no extra charge.

        Also, I’ve got a new vs. KICKSTARTER campaign that is currently running. That’s over at kickstarter.com/projects/denaghdesign/vs-kickstarter-2-more-small-roleplaying-games — and yes, there will be phone pdfs of those four games available, too!

        Thanks again for your kind words!

        Liked by 1 person

  2. The part I’m really wondering about… Epub.
    It already does everything phone PDF is aiming for, in a more customizable format that is MUCH less demanding on system resources

    Liked by 1 person

    1. The ePub format has two serious drawbacks: presentation and translation costs. With the presentation, the format varies greatly from reader to reader: standardizing the width of tables and statblocks and sidebars in a epub so all the relevant data can be shows on screen can be time consuming and challenging. With the feedback I’ve received from some publishers (no actual data, just generalizations), there doesn’t seem to be a market for epubs that is worth pursuing. (The cost of translation just doesn’t seem to meet the demand.)

      A friend of mine (also does layout) is attempting to see if using the same InCopy file (ie: just the book’s text that has been tagged with markup for bolding, italicizing, and other formatting) would work shared between two InDesign files (ie: the physical format and look and feel). So far it sounds like it would work, which drastically reduces the time and cost spent on translating a printed book to a smaller format.

      However, getting back to the market for these formats, I still don’t believe that there is one for a full rpg book done this way. An extended GM screen or player reference booklet maybe? But I still doubt I’d want to read something like Pathfinder 2 on a phone.

      (Also: wow, I just saw that my earlier posts used an old old old WordPress bio. Gotta fix that.)

      Liked by 2 people

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.