Routers are powerful tools in Single Page Applications, and Kendo UI's
router provides an API to wrap up this power.
But the API hides a lot of potential complexity and performance
issues if you're not careful. Calling the navigate method
without regard for the current context of the application and whether
or not that context is changing can result in unwanted re-rendering
of the entire application. This can reduce the responsiveness of the
app, waste time re-drawing content that isn't changing, and cause a
lot of flickering on the screen - and none of this is desirable
from a user's perspective.