You can play content on iPad. Since iPad uses the iOS operating system, some adaptations were made to the Player.
You cannot record content for iOS applications so all content will be of Windows-based applications. Recorded topics could have such steps as double-clicks, right mouse clicks, and keyboard events that have no equivalent on iOS such as "Press ENTER". Users should be aware of this.
To help solve the problem mentioned in the previous bullet, special templates have been created for playback on iOS. These templates tell the user to "Swipe left to continue", rather than "Press ENTER to continue". In addition, for all unsupported actions such as mouse clicks and keyboard events, the user can advance using swipe left. Of course, the user can always tap in the action area for a step. The first time a user launches a topic in each session, a message displays instructing users to use swipe left to advance. This message only appears once.
If an Adobe Acrobat (.pdf) file is attached to a concept in the Player outline, the file does not scroll on iPad. To enable scrolling, an Open in New Window link appears in the Player window. This opens the file in a new window, in which scrolling is enabled.
Content can be installed in Knowledge Center and launched through the Player link. Usage is tracked. Also, if the content is installed in Knowledge Center and the user is directly launching the content from the content root, then usage is tracked.
If the font for string inputs, bubble text, or web pages is MS Sans Serif or Tahoma, a font substitution is made automatically, as these fonts do not exist in an iPad environment.
The Share feature works differently on iPad. If you navigate to a topic and use the Share feature, you get a link that when opened shows the topic page with the play mode buttons. However, if you navigate to the concept for a topic and use the share feature, you get a link that when opened shows the concept page and does not show the play mode buttons.
To play sound on an iPad, the following MIME type must be registered on the server where the content is deployed. If the content is deployed on a Knowledge Center server, the MIME type is already present.