When you make a change to user-interface code, how do you know if it does what you expect? How long do you have to wait between typing some code, hitting refresh, and then seeing the result?
There are popular tools to speed up this refresh cycle, but what about user interaction or multiple component states? Even with auto-refresh or hot code reloading you'll usually still have to click on a button to check if your animations are working correctly.
I'll show you how you can get an even better level of immediate feedback from changes. One that lets you see the variety of possible states and interactions your components have all at the same time. This can vastly improve our experiences when building interactive web applications.
Not better, just volunteering some random thoughts:
The omniscient front-end developer
As front-end developers we handle many different component states, but a user-interface is not static: we must interact with our code and watch for feedback as we drag items and click buttons.
What if we could go beyond hot code reloading and see immediate feedback on multiple component states and interactions? ...