Client-side routing

Our Master/Detail relationship is indeed working, yet it has some major flaws. The current in-page navigation approach, for example, is completely different from the original plan. We wanted our users to switch back and forth between the HomeView containing the list of quizzes and a dedicated QuizView whenever he selects one of them, but the app doesn't do that; it just opens something like a "quiz detail panel" under each list. Not just one but three different panels, one for each item lists--that doesn’t make any sense! We need to fix that as soon as possible.

While doing that, we also have another issue to solve. You may have noted that, regardless of what we do within our app, the URL in the browser's address bar is always the same. It will mean that we won’t be able to share, say, a URL that will directly lead to a specific quiz; we’ll be forced to share the starting URL because it is the only supported one.

Wait a minute, isn’t this our Native Web application’s most...