Defining your Goals and Limitations
When you think about digital publishing, it's easy to assume that your first questions should be:
-
Which devices do I want to publish to?
-
What format do I want to publish in?
-
Which tools do I want to use?
However, this may not be the best place to start. Different devices, formats, and tools have different strengths and weaknesses, and it's difficult to choose from among them unless you have a clear picture of your goals, needs, and limitations. The topics below can help you to get a better fix on these, so you can make an intelligent decision when it comes time to choose a direction.
Characterizing your content
To some extent, the choices you make about devices and format should depend on the nature of your content. Is your content highly designed, like a magazine or a brochure? Is it primarily textual, with just a few pictures? Is it designed primarily for visual impact, or for leisurely reading? The answers to questions like these can help you decide whether you need layout view, or reflow view, or both.
-
A fixed layout view lets you carefully design pages for maximum visual impact, and allows you to include multimedia content such as sound and movies. A layout view also lets you maintain your branding to the greatest degree possible, because it provides maximum flexibility.
-
A reflow view displays text and pictures only, usually with a user-controllable text size and font. A reflow view is less flexible than a layout view, but may be desirable because it makes it easy for the customer to read the text without distraction. Reflow view is well-suited to traditional books and reference materials.
If your content is designed to make a strong visual impression, if you need to maintain your branding, and if you want to include multimedia components, you might want to consider creating a fixed layout ePub, HTML5 Publication or a custom app, or using App Publishing Studio to create content that can be viewed in a custom reader app.
If your content is primarily textual, and you don't have any need for fancy layout, you might want to consider using a format such as reflow ePub eBook. This format provides only a reflow view, and is compatible with a wide variety of readers.
If it is critical that your content be presented in a way that is uniquely yours, you can create a custom app which is the most labor intensive. Or you can use App Publishing Studio which is much easier. App Publishing Studio offers the most common features you may need, and you no longer need to build an app from scratch. Out of the box, App Publishing Studio supports multiple platforms and allows for personalized branding and presence in the app stores without the expense of creating and maintaining a custom app.
Another question you may want to ask yourself is, do you want or need to support multiple device orientations? Do your customers expect this functionality? If this is important to you, you should probably consider this when choosing a format. Many ePub readers support this functionality automatically, but not all of them. If you want to vary your layout when the orientation changes, a better choice would be a custom app or an issue created in App Publishing Studio. Apps and webapps (HTML5 publication) support multiple variants (aspect ratios) for various device sizes. For example, you can create fixed layouts that fit iPad and iPhone screens and automatically render the right variant based on the device you are using.
If you're considering using multimedia elements such as audio and video, make sure you have the resources necessary to produce those multimedia assets. It's easy to get excited about the idea of using multimedia, but creating and using multimedia properly can involve a great deal of planning and expense. You may be able to reuse materials that your organization has already created for other media, such as the organization's Website.
Some other things to think about:
-
Do you want to provide your users with industry-standard navigation controls and icons that they can use without having to think about it too hard, or do you want to create custom controls that provide a more unique experience?
-
Do you plan to deliver the same content on the Web? If so, what (if anything) should differentiate the Web version of the content from the version delivered on handheld devices? If there are no meaningful differences between the presentation of content on your Website and the presentation of that content on a handheld device, you may want to consider whether you need an app experience at all.
-
Do you need to publish in multiple formats, or only in an app presentation? Are you porting content from another format? Can you do a single-source approach, at least to generate the initial version of a layout that you can then customize for release as an app issue?
For more information about the formats discussed here, see "Hardware, Operating Systems, and Formats".
Assessing your customers' needs
It's probably safe to assume that you want your customers to have a positive experience with your content. To make sure this happens, consider questions such as the following:
-
Do your customers want to be able to change the point size of the text? If so, consider a format that includes a reflow view.
-
Will your consumers be able to download your content when they want to? For example, if you want to download an app and its content over a low bandwidth (like mobile networks), you want to make sure that the app is downloadable easily. You can consider a light-weight format such as ePub or try to minimize the size of any multimedia assets you include in your apps.
-
How quickly will your customers want to be able to download your content? Even on an unrestricted network, you might want to think about keeping the size of your files as small as possible, in order to prevent your customers from becoming frustrated with the wait.
-
In what languages do your customers want to read your content? If you want to distribute content in multiple languages, you should make sure that the format and device you choose support those languages. For example, some East Asian and Eastern European languages use characters that are not available in many Western fonts, and some languages are read in different directions than Western languages. The ePub format supports East Asian and Eastern European languages on some devices, but it may not support them on all devices. If you want to use App Publishing Studio, you must use only the layout view, because special characters may not display correctly in reflow view.
-
Do you expect your customers to have an Internet connection when they're consuming the content? If so, you should make sure your content behaves gracefully when customers don't have access to a network. If you create HTML5 interactivity, you can provide a default or "fallback" image or other graphic element in each spot where you display content live via the Web.
For more information about the formats discussed here, see "Hardware, Operating Systems, and Formats."
Planning for distribution
Just as there are different ways to distribute print content, there are different ways to distribute content for handheld devices. The way in which you choose to distribute your content probably depends on what that content is for and how you plan to generate revenue.
Consider how often you plan to release content:
-
Do you need to distribute small amounts of content on a frequent basis? If so, you might want to consider publishing content on News reader apps like Apple News, Flipboard, etc. This approach gives you continuous publishing, and revenue can come from both advertisements and the content you publish.
-
Do you want to publish content for sale on an infrequent or irregular basis? For example, are you a publisher who wants to make book titles available to your customers? If this is the case, you may want to consider using the ePub format. If you have no need of layout view, you might consider a large existing distribution network such as Amazon or Apple iBooks, or one of many smaller distribution networks.
-
Do you want to sell published content on a recurring basis? For example, are you creating a digital magazine? You can accomplish this by creating a custom app for each issue, but this can be work-intensive, and some customers may not want to download a new app every time. You can also consider creating an App Publishing Studio reader app, and then selling individual issues from a Web server. If you choose this approach, you can customize the app to display your branding, or use a generic viewer app. (Note, however, that this approach limits you to the platforms supported by App Publishing Studio.)
If you choose to distribute App Publishing Studio issues that are viewable in a reader app, you should consider whether you want to make a sample issue available so that the user can experience the value of your publications. You can bundle a sample issue with the app, but if you do so be wary of file size, both for reasons of download size restrictions and to avoid making your customers wait too long. You can also provide free access to a sample issue from within the reader application.
Of course, you need a plan for generating revenue. The options here include selling apps on an individual basis, selling issues that can be viewed in a reader app, selling books (for example, for iBooks), and selling advertising. If you choose to sell advertising, you can work out individual deals with advertisers, or use an existing ad network such as Apple's iAd (for iOS only) or Google AdMob (for iOS and Android).
When you're thinking about advertising, you might also want to think about analytics. Do you want your app to provide you with information about how it's being used, and how your content is being consumed? Both iAd and AdMob include options for gathering such information and using it to tailor advertising.
Finally, how different platforms do you want to deliver on? Here, custom apps are the least appealing option, because they must be written separately for each platform. For maximum coverage, consider an industry standard format such as ePub or HTML5 Publications.
For more information about the formats discussed here, see "Hardware, Operating Systems, and Formats."
Assessing your infrastructure needs
Creating content for digital distribution is only one part of the digital publishing process. If you plan to deliver content for digital devices, you need to make sure that you have all the infrastructure necessary to do so.
For example, if you plan to host content on a Website, you need to consider how much space you're planning to need and how many downloads you anticipate having, because both of these typically affect the amount you are charged for hosting. In any case, you should track your usage information once you have launched, analyze it, and make any necessary adjustments to your hosting plan. (If you create an app that includes content served over the Web, you should also consider the hosting plan used for that content.)
Billing is another important aspect to consider. If you are selling individual apps or issues, you need to make sure you have the infrastructure necessary to take payments for that content in every market where you want to make that content available. Probably the easiest way to do this is to use an established network such as the App Store or Amazon, because these organizations are designed to make this aspect of business easy and transparent for content creators.
Finally, you should probably have a plan for promoting and marketing your content. You can hire an expert to handle this for you, or promote your content yourself using social media such as Facebook and Twitter, or you can do a combination of both.
