The Fully Browser
loadUrl() approach works, but when using the built-in “dashboard” tile, it is so much faster/nicer.
Even when I use the “fast” client-side navigation (e.g.
loadUrl() approach is tolerable, but it makes me try not to use this approach if at all possible. The WAF went up when I just had dedicated buttons for different dashboards rather than one button that triggered a rule that went to one dashboard or the other based on a variable (which indicated whether music was currently playing).
I’m not sure how - internally - dashboards switch that is different than the loadUrl() approach, but there is seems to be something clever going on.