One thing their example doesn't handle is browser location history on clicking elements in their UI.
Maybe it was due to how simple the example was, but having to click back many times based on how many times a user used the interface is just bad design.
Sorry about that, the example was developed as a standalone SPA with history for the routing. But since we decided to embed it into the blog post itself, the pushState routing doesn't make a lot of sense in that context.
Maybe it was due to how simple the example was, but having to click back many times based on how many times a user used the interface is just bad design.