The user interface structure

Our e-book application comprises a single landscape window, with each page of the book represented as a view that will occupy the entire screen's real estate. All pages will be stacked atop each other and will be shown (or hidden) depending on the current page. We will delegate this page management mechanism to the Page Flip Native module, which will do all the heavy lifting for us. Therefore, all our View pages will be wrapped in the PageFlip component.

Here, the e-book example shown will have only three pages for the sake of this chapter, but you can apply these basic principles on a much bigger scale. The pages are represented as:

• A WebView page referencing a local HTML page

• A MapView page configured to display a specific geographical region

• A VideoPlayer page to play a local video MPEG file