Basically, we have to provide an information message to the user in scenarios where the browser doesn't have the support for impress.js functionality. This is handled by the core code inside the library. Handling browser fallback methods and customizations will be discussed in Chapter 6, Troubleshooting.
Providing a fallback message doesn't mean we are done with handling impress.js for mobiles. Effects such as scaling, transforms, and rotations might not work on those devices. Still, the user should be able to read the whole content of the presentation without encountering any issues.
Let's go through some impress.js presentations on mobile devices to figure out the common problems in designing for mobiles.
The images shown here are taken from a presentation in the demo section of the impress.js github page. Obviously, it is being designed for impress-supported browsers. You can take a look at the presentation at http://johnpolacek.github.com...
