Q: What do we think of Flash vs. HTML5?A: Flash is not supported on most mobile devices including Apple’s iPhone or iPad, meaning that other technologies must be used to support rich media like video these devices. HTML5 supports video playback and has the advantage that no 3rd party plug-in is required. We selectively uses HTML5 and CSS3 tags in our mobile viewers and we will continue to support Flash for all desktop, notebook, and netbook devices. If Flash becomes more widely available on mobile devices we will look to support Flash on these devices.
Q: Is Flash going to die?
A: Flash is available on more than 98% of all computers, which makes it the most widely used content platform for interactive rich content on non-mobile devices. Flash is starting to make headway into mobile devices but the adoption rate is still low. We will continue to support Flash for all desktop, notebook, and netbook devices. If Flash becomes more widely available on mobile devices we will look to support Flash on these devices.
Q: Are we going to continue to support Flash?
A: Yes, we will continue to support Flash for all desktop, notebook, and netbook devices. If Flash becomes more widely available on mobile devices will also look to support Flash on these devices.
Q: Why is a browser-based version the best for our customers?
A: Since our Mobile is browser-based, readers do not need to download an App before they read a publication, therefore making publications readily available to readers which can positively impact readership. In addition, a browser-based application is not subjected to Apple’s approval process.
Q: Are we going to build Apps?
A: Apps can do things browser-based solutions cannot do. Apps, however, are platform specific and require us and our customers to support two or more Apps to cover the same market. Our goal is to maximize the reach of our customers’ publications; therefore, we chose to first build a solution that enables the broadest mobile platform coverage. This solution offers the look and feel of an App in a browser-based solution. Mobile publications will appear on the readers Home Screen, if they bookmark it to their Home Screen from the browser. In the future, we may build apps for specific platforms if this would benefit our customers.
Q: What was the design intent for the Mobile viewer ?
A: The primary goal to optimize the user experience on mobile devices. The typical use cases include:
1. searching in the browser, finding and clicking on a link;
2. receiving an email with a link and clicking on the link;
3. clicking on a link directly from a website.
A reader must be able to see a publication without the need to install an Application. The definition of good user experience is different depending on the device. On a small mobile phone, users want speed and simplicity and on a laptop, users expect a rich,interactive experience. Our Mobile viewer is accessible, fast, and simple.
Q: What is our mobile road map?
A.Our mobile road map includes continued development of capabilities that improve the reading experience. We will continue to take advantage of the best technology and capabilities on the platforms readers prefer.
Q: When will we support Windows 7 mobile, Blackberry and the other mobile OS?
A: Apple and Android smart phones and tablets account for more than 80% of the data traffic in North America and Europe. We will continue to listen to our customers’ needs and will continue to evaluate support for multiple mobile platforms.
Q: Why is Mobile platform a beta release?
A: The Mobile Beta is a robust, production quality release. Customers can use it in production environments. The Mobile Beta offers a simple, seamless, and fast user experience. As we expand the capabilities of the mobile viewer, we will remove the Beta tag.
Q: Do we have to create 2 different versions of our digital publications?
(one for the flash-based viewer and another for the mobile viewer)
A: No, the mobile viewer is compatible with Flash-based publications and catalogs optimized for desktop PCs. With our ploatform, organizations can create a publication once and deliver to their audience on multiple devices in the best viewing format.
Q: Is the Mobile Beta backwards compatible ?
A: All V3 viewer publications are directly available on mobile devices. The publications will have the same URL/links immediately doubling the reach of existing published content.
Q: What are the interactive features of Mobile Beta?
A: Our Mobile Beta supports high quality zooming (tapping and pinch), touch navigation (slide) and automatic conversion from single page to split pages (spreads) when the smart phone / tablet is rotated. Our goal was to use standard navigation and view features that mobile browsers support.
Q: Why did we not include all basic features?
A: The mobile user has different expectations with regard to content and content accessibility than a desktop user. Quick access to relevant content takes priority over a multitude of interaction modes, this means that mobile navigation functionality like slide and pinch zoom takes priority over using valuable screen real estate for table of contents, download to PDF etc.
Q:How will Mobile Beta display embedded links, videos, Flash?
A: In the Mobile viewer all links, videos, Flash, and forms will be deactivated. If you have these in your flash version, then they simply will not show up in the mobile version. What you will see is what is on the original PDF page, behind the elements.
Q: Are embedded viewers supported on mobile devices?
A: Embedded viewers are currently not supported. When a visitor navigates to a web site that contains an embedded viewer, he/she will get the same experience on a smart-phone as before with the Mobile Beta release. The Viewer API has not been changed as part of the release.
Q: Will archives work for mobile publications?
A: Mobile archives will be deactivated. If you have these in your flash version, then they simply will not appear in the mobile version.
Q: Are security features supported?
A: Security features are currently not supported. When a visitor attempts to open a viewer that has enabled access control features, he/she will be informed that the publication is unavailable for mobile devices.
Q: Is Page 0 supported in the mobile viewer?
A: Page 0 (aka “Intro page”) is not supported on mobile devices. The customer generated page will most likely not fit into the available space for the mobile viewer. Also, the ‘page 0’concept requires that the publication is viewed in a spread, something that requires to be in landscape orientation.
Q: Is it possible to customize the mobile viewer?
A: Currently has one mobile viewer and it is not possible to create custom viewers. The current implementation has been designed with future mobile viewer configuration in mind.
Q: Android 2.2 supports flash; why show the HTML5 version on that device?
A: Our Mobile supports Android 1.5, 1.6, 2.1 and 2.2 (99.6% of the devices). Android 2.2, devices which have downloaded the Flash Player from Android Market will be able to render Flash content. However, since the Flash Viewer is optimized for desktop resolution (min. 1024x768px) and mouse/keyboard interaction, the Mobile Beta will still deliver a far better experience on mobile devices. Therefore, all Android devices will default to the Mobile Beta, which is optimized for mobile resolution (min. 240x320 px) and touch interaction.
Q: Is the preview feature available on mobile viewers?
A: Yes, the preview feature is available using the same URL as the Flash Viewer. Since the Publicator is not optimized for mobile devices, the easiest way to get the URL to mobile device is to email it or type it in.
Q: Does the “refresh on CDN” work for mobile publications?
A: Yes
Q: How long does it take to refresh mobile publications on the CDN?
A: The desktop and mobile publications are refreshed using the same technology
Q: Can you use the redirect feature on a mobile edition
A: Redirects are not supported in the initial release
No comments:
Post a Comment