How to Get Paid for your Digital Publications without Breaking the Bank

I recently received an email containing the following questions:

Your product [in5] looks amaaazing!

One issue that has always hassled me is the deployment, monetization and DRM [Digital Rights Management] side of things. Do you have any solutions like this for clients selling their creations?

…Aside from the vastly expensive DPS hosting and app store – there don’t seem to be any options available for the small guy to monetize a digital document…?

These are good questions that I believe are of interest to many people. There are several affordable ways to monetize your content and provide some protection to your content at the same time. I’ve put together a list of the best options below (and more are sure to pop up).

1. Host Content Behind a Paid Firewall

Hosting the web content produced by in5 behind a paid firewall (i.e. users pay a membership fee which gives them access to a private part of a website) is a simple way to collect revenue and can provide some basic DRM. Only paid members would have access to the site (via username and password) and content would remain on the server.

Taking the output into app form can also provide revenue (through an app store) and DRM (since apps can be difficult to distribute outside of a store). The options that follow all involve creating an app(s).

Check out this video course on creating a membership site. It uses WishList Member and WordPress to create private areas on your site and lets you easily accept payments.

Amazon HTML52. Submit Directly to Amazon

You can submit in5 content directly to Amazon. Amazon will actually do the packaging for you! The app is then available to Kindle Fire and several Android devices through the Amazon AppStore. A developer account and app submission are both free. Doesn’t get more affordable than that. (demo video)

3. Create an App Using the Baker Framework*

You can also export to the Baker Framework using in5, and then package as a app for iPhone or iPad. The Baker Framework is an open source library (completely free) for Xcode (the Apple developer code editor, which is free, but requires a Mac) that can produce a standalone app or issues for Apple Newsstand. An Apple Developer license is $99/year (and up) and if you charge for your app (or Newsstand issues), I believe Apple will take a percentage. (demo video)

Update: Baker Framework is not currently being maintained, so I recommend using PhoneGap Build (described in the next option).

PhoneGap4. Package as an App using PhoneGap*

You can also package in5 output as an app for multiple devices using PhoneGap. The core of PhoneGap is based on a free, open-source product and there is also a nice web service called PhoneGap Build—which is free with an Adobe CC subscription, and super easy to use!

Check out the Create a Mobile App with in5 & PhoneGap Build course for detailed steps on creating a mobile app (without coding) using PhoneGap Build.

5. Use a premium service*

While a premium service, like Paperlit, will cost you more than options above, it will still let you create your app content with HTML, making the development process much cheaper. This type of service all comes with several premium features and is great for multi-issue magazine apps.

*There are some costs associated with submitting to the app stores (I believe is the most costly is Apple’s at around $99/year for a single developer) which are separate from the product or service that does the “packaging” for you.

Mobile App Design and Submission has Never Been This Easy

I mentioned a while back that Amazon had quietly revolutionized the app creation process by allowing submission of HTML5 apps to their marketplace. Very few people understood the significance of this change which allows people to publish without the burden of going through the traditional app production process. So I’m going to cover this topic a bit more within this post. Firstly, what does the existing process of creating and submitting an app to an app store look like?

The Typical App Submission Process

The steps required to create and submit an app vary depending on the tools you’re using and the app store you’re submitting to, but the steps go something like this:

  1. Pay for a developer account (recurring annual fee).
  2. Use your developer account to produce a code-signing certificate (a way to verify that you paid to publish).
  3. Insert the signing certificate into your app.
  4. If you’re a coder, compile your app. If you’re not a coder, pay some service or developer to compile your app.
  5. Submit your app to the app store and wait for approval.

The New Process Created By Amazon

Amazon essentially reduced this process to a single step: submit your content to the app store. No fee, no signing-certificate, no packaging, no need to know a heavy-duty programming language or to pay someone who does. Your content just has to be in the form of HTML.

I don’t think it was clear to many people just how easy Amazon’s app submission process has now become, and how favorably it compares to other options.

Thankfully, David Isbitski, recorded a video on how to submit an HTML5 Web App to the Amazon Marketplace:

Unlike other app stores, getting an Amazon Developer account and submitting an app is totally free!

Don’t know how to create HTML5? No problem.

You don’t need to be a web developer to take advantage of Amazon’s HTML5 app submission process. You can export HTML5 directly from InDesign using in5, upload your content to a server and submit the URL directly to Amazon. InDesign to app! No programming knowledge required and no recurring costs.

How in5 makes it even easier

When creating content with InDesign and in5, you can simply enter the Amazon Verification Key into the in5 dialog and in5 will even generate the web-app-manifest.json file for you so that you can focus entirely on the design of your app (and not programmer-type things like “manifest” files).

Here are the two fields that are available in the SEO & Meta section of the in5 dialog:

in5 Amazon options

Take a look at in5 and the Amazon HTML5 submission process and let us know what you think in the comments below.

The Most Useful in5 Feature that You’re Not Using Yet – Scaling a Single Design to Multiple Devices – The Viewport Zoom Setting Explained

The Viewport Zoom Setting can be used to control how your design scales automatically on mobile devices (tablets and smartphones). This video below provides a tour of versatile Viewport Zoom options and shows the results displayed on the screens of multiple devices.

Update: in5 now has sophisticated proportional scaling for all devices.
Learn more about scaling with in5

Local Playback of YouTube Embeds

The easiest way to embed a YouTube video in another webpage is to use Share > Embed, found on any YouTube video page.

YouTube has recently made a slight modification to this code by removing the protocol (http:) at the beginning of the URL:

<iframe width="560" height="315" src="//www.youtube.com/embed/CBfVgQNKa5s" 
frameborder="0" allowfullscreen></iframe>

In many respects, this an improvement. The lack of a a protocol means that this link will inherit the protocol from its container page. So if the container page is https (a secure page), the YouTube video will be as well. This avoids a security warning to IE users when loading unsecured content (the http YouTube video)  within a secured (https) webpage. This is a more flexible method, as long as your page is on a web server.

However, it means that the embedded content will not preview locally from your hard drive.

To view a working embed from you local drive, modify the embed so that the src attribute begins with http:

<iframe width="560" height="315" src="http://www.youtube.com/embed/CBfVgQNKa5s" 
frameborder="0" allowfullscreen></iframe>

The same protocol policy goes for URLs used with Google’s Hosted Libraries (like jQuery).