Navigators and views

Navigators are architectural sugar. In previous examples we have coded all the navigable components in line. For instance, Page 1 and Page 2 are merely labels. In real Vaadin applications for men and women, we would need to code a complete class for a page, maybe several classes. So Page 1 would need its own class. The same happens for Welcome page and Page 2. The web developer will start scratching her or his head more frequently as more classes (pages) are added to the application. Complexity will grow to the point that maintaining the application would let our developers bald. Vaadin worries about programmers' hair (or skin if they are bald) and have incorporated the Navigator class and View interface.